From owner-freebsd-current@FreeBSD.ORG Tue Jul 26 13:58:27 2005 Return-Path: X-Original-To: current@freebsd.org 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 5990516A41F for ; Tue, 26 Jul 2005 13:58:27 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id E04EB43D53 for ; Tue, 26 Jul 2005 13:58:17 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 26795617E; Tue, 26 Jul 2005 15:58:12 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 169146149; Tue, 26 Jul 2005 15:58:12 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 0289433D42; Tue, 26 Jul 2005 15:58:12 +0200 (CEST) To: Luigi Rizzo References: <20050726065444.A37735@xorpc.icir.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Tue, 26 Jul 2005 15:58:11 +0200 In-Reply-To: <20050726065444.A37735@xorpc.icir.org> (Luigi Rizzo's message of "Tue, 26 Jul 2005 06:54:44 -0700") Message-ID: <86mzo94qks.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Tests: ALL_TRUSTED,AWL,BAYES_00 X-Spam-Learn: ham X-Spam-Score: -5.3/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on tim.des.no Cc: s223560@studenti.ing.unipi.it, current@freebsd.org Subject: Re: multiple pending filesystem requests for the same block ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 26 Jul 2005 13:58:27 -0000 Luigi Rizzo writes: > can the filesystem code have multiple pending write requests for > the same disk block ? This was discussed on the lists a few weeks ago, and ISTR the conclusion was that it is the filesystem's responsibility to ensure this never happens. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no