From owner-freebsd-hardware@FreeBSD.ORG Tue Oct 12 21:03:50 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 047F516A4D1 for ; Tue, 12 Oct 2004 21:03:50 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EF4743D45 for ; Tue, 12 Oct 2004 21:03:49 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id i9CL3kMH088913; Tue, 12 Oct 2004 15:03:46 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id i9CL3krU088912; Tue, 12 Oct 2004 15:03:46 -0600 (MDT) (envelope-from ken) Date: Tue, 12 Oct 2004 15:03:46 -0600 From: "Kenneth D. Merry" To: David Gilbert Message-ID: <20041012210346.GA88834@nargothrond.kdm.org> References: <20041011043508.GA72113@nargothrond.kdm.org> <20041011210303.GA78436@nargothrond.kdm.org> <16747.63803.470649.921882@canoe.dclg.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16747.63803.470649.921882@canoe.dclg.ca> User-Agent: Mutt/1.4.2i X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on nargothrond.kdm.org X-Virus-Status: Clean cc: Roisin Murphy cc: freebsd-hardware@freebsd.org Subject: Re: sata raid & write cache state X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 21:03:50 -0000 On Tue, Oct 12, 2004 at 11:33:15 -0400, David Gilbert wrote: > >>>>> "Kenneth" == Kenneth D Merry writes: > > Kenneth> See my previous mail. SATA disks differ in two ways: > > Kenneth> 1. Many don't support tagged queueing. > > I'd like to see more information on this. I was under the impression > that SATA required some form of command queueing in all drives. > > Kenneth> 2. If the SATA disk does support tagged queueing, there is > Kenneth> still a fundamental problem with the queueing model in SATA > Kenneth> (and probably ATA, not sure). According to a coworker of > Kenneth> mine (hardware engineer) who is a SATA expert, the status > Kenneth> phase on the bus is the same phase as the data phase. So you > Kenneth> basically have to send all the data to the drive on a write > Kenneth> and the drive has to send the status back before the drive > Kenneth> can accept any more data for another queued write command. > Kenneth> So that limits you, effectively, to writing data for one > Kenneth> command at a time. > > It would appear that the SATA folks are introducing 'NCQ' (Native > Command Queueing) ... which does supply out-of-order returns among > other things. >From talking to my co-worker again, it sounds like the SATA II spec does allow breaking up the data and status phases for a command. (i.e. out of order command completion) The key is that even if the drive supports it, the controller has to enable that feature on the drive. So the bottom line is that with a drive and a controller that support SATA II NCQ and out of order completion, you could disable write caching on the drive and still (in theory) get reasonable performance out of it. Ken -- Kenneth Merry ken@FreeBSD.ORG