Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753894AbYJFNus (ORCPT ); Mon, 6 Oct 2008 09:50:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752025AbYJFNuk (ORCPT ); Mon, 6 Oct 2008 09:50:40 -0400 Received: from casper.infradead.org ([85.118.1.10]:49350 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752004AbYJFNuk (ORCPT ); Mon, 6 Oct 2008 09:50:40 -0400 Date: Mon, 6 Oct 2008 06:50:24 -0700 From: Arjan van de Ven To: Mikulas Patocka Cc: Andrew Morton , linux-kernel@vger.kernel.org, agk@redhat.com, mbroz@redhat.com, chris@arachsys.com Subject: Re: [PATCH 2/3] Fix fsync livelock Message-ID: <20081006065024.380d1d00@infradead.org> In-Reply-To: References: <20080911101616.GA24064@agk.fab.redhat.com> <20080923154905.50d4b0fa.akpm@linux-foundation.org> <20080923164623.ce82c1c2.akpm@linux-foundation.org> <20081001225404.4e973465.akpm@linux-foundation.org> <20081005153306.7e644c9f@infradead.org> <20081005160724.54dd1a27@infradead.org> <20081005162847.7bf0ead1@infradead.org> <20081005173019.0a358b09@infradead.org> <20081005212031.63ad246a@infradead.org> Organization: Intel X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.12; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by casper.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1134 Lines: 30 On Mon, 6 Oct 2008 09:00:14 -0400 (EDT) Mikulas Patocka wrote: > On Sun, 5 Oct 2008, Arjan van de Ven wrote: > > > On Sun, 5 Oct 2008 23:30:51 -0400 (EDT > > > The point is that many fsync()s may run in parallel and you have > > > just one inode and just one chain. And if you add two-word > > > list_head to a page, to link it on this list, many developers > > > will hate it for increasing its size. > > > > why to a page? > > a list head in the inode and chain up the bios.... > > And if you want to wait for a bio submitted by a different process? > There's no way you can find the bio from the page. the point is that the kernel would always chain it to the inode, independent of who or when it is submitted -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/