From owner-freebsd-current@FreeBSD.ORG Mon Jul 26 22:20:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C52516A4CE; Mon, 26 Jul 2004 22:20:26 +0000 (GMT) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id D394843D1F; Mon, 26 Jul 2004 22:20:25 +0000 (GMT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id i6QMKNQD098914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.lcs.mit.edu issuer=SSL+20Client+20CA); Mon, 26 Jul 2004 18:20:24 -0400 (EDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.9/8.12.9/Submit) id i6QMKMT0098911; Mon, 26 Jul 2004 18:20:22 -0400 (EDT) (envelope-from wollman) Date: Mon, 26 Jul 2004 18:20:22 -0400 (EDT) From: Garrett Wollman Message-Id: <200407262220.i6QMKMT0098911@khavrinen.lcs.mit.edu> To: Scott Long In-Reply-To: <20040726155712.R32601@pooker.samsco.org> References: <1090718450.2020.4.camel@illusion.com> <200407251112.46183.doconnor@gsoft.com.au> <20040726175219.GA96815@green.homeunix.org> <20040726155712.R32601@pooker.samsco.org> X-Spam-Score: -19.8 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES X-Scanned-By: MIMEDefang 2.37 X-Mailman-Approved-At: Mon, 26 Jul 2004 22:41:55 +0000 cc: current@FreeBSD.ORG Subject: Re: magic sysrq keys functionality X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 22:20:26 -0000 < said: > This works right now because we assume that disks will commit blocks > in order, and that assumption generally hasn't been broken. I don't think soft updates cares about what order blocks are committed, because it will not in general consider a dependency resolved until it is notified that the buffer has been written. What we do assume is that the disk (or driver) doesn't lie to us and claim that a block was written when it really wasn't. -GAWollman