From owner-cvs-all Tue Dec 7 1:11:46 1999 Delivered-To: cvs-all@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3487614D79; Tue, 7 Dec 1999 01:11:43 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id BAA01780; Tue, 7 Dec 1999 01:11:42 -0800 (PST) Date: Tue, 7 Dec 1999 01:11:41 -0800 (PST) From: Julian Elischer To: Matthew Dillon Cc: Mike Smith , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern kern_shutdown.c In-Reply-To: <199912070829.AAA75674@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On Tue, 7 Dec 1999, Matthew Dillon wrote: > > The disk can lie about whether it has written data to the disk without > messing softupdates up, but it cannot reorder writes that the system has > told it must be ordered. SCSI has a tag to guarentee ordering (or not), > but I don't know if IDE has the same sort of feature. Softupdates ensures the ordering by not isuing a dependent write until it is told that the dependency write has completed. Thus, if the drive says a block is written but it is really in cache, and the system issues another write that depended on the first, the second must not be able to 'overtake' the first. THe safest way to guarantee this is to just not allow the situation to occur. > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message