From mboxrd@z Thu Jan 1 00:00:00 1970 From: Werner Almesberger Subject: Re: [Ext2-devel] Reviewing ext3 improvement patches (delalloc, mballoc, extents) Date: Mon, 14 Mar 2005 13:37:23 -0300 Message-ID: <20050314133723.L12802@almesberger.net> References: <20050303083349.GA4896@in.ibm.com> <1109898734.4961.11.camel@dyn318077bld.beaverton.ibm.com> <1109900773.4637.9.camel@dyn318043bld.beaverton.ibm.com> <20050314053658.A12360@almesberger.net> <20050314090414.GA4164@in.ibm.com> <20050314120240.K12802@almesberger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Suparna Bhattacharya , Mingming Cao , Badari Pulavarty , ext2-devel , linux-fsdevel@vger.kernel.org, abiss-general@lists.sourceforge.net Received: from host.almesberger.net ([204.10.140.10]:18191 "EHLO host.almesberger.net") by vger.kernel.org with ESMTP id S261584AbVCNQkg (ORCPT ); Mon, 14 Mar 2005 11:40:36 -0500 To: Alex Tomas Content-Disposition: inline In-Reply-To: ; from alex@clusterfs.com on Mon, Mar 14, 2005 at 06:43:02PM +0300 Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Alex Tomas wrote: > I see no reason to reserve specific block in ->prepare/->commit in > delayed allocation case. We already do this with reservation. This seems like a sensible approach to me. Trying to reserve specific blocks in an FS-independent way was what got us in trouble on ABISS. So the plan B is to add this kind of reservation to where it is really lacking (i.e. FAT). Hmm, it's a bit confusing that we call both things "reservation". Well, airlines do this too, "free seating". > locked during writeback? PG_writeback should be used instead of PG_locked. In mpage_writepages, writepage can also get called with the page just PG_locked. - Werner -- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina werner@almesberger.net / /_http://www.almesberger.net/____________________________________________/