From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Tomas Subject: Re: Lazy block allocation and block_prepare_write? Date: Tue, 19 Apr 2005 14:10:13 +0400 Message-ID: References: <8e70aacf05041717546fdff3f@mail.gmail.com> <42647484.5040208@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Martin Jambor , linux-fsdevel@vger.kernel.org Return-path: Received: from [83.102.214.158] ([83.102.214.158]:23981 "EHLO gw.home.net") by vger.kernel.org with ESMTP id S261444AbVDSKLo (ORCPT ); Tue, 19 Apr 2005 06:11:44 -0400 To: Badari Pulavarty In-Reply-To: <42647484.5040208@us.ibm.com> (Badari Pulavarty's message of "Mon, 18 Apr 2005 20:01:24 -0700") Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org >>>>> Badari Pulavarty (BP) writes: BP> In order to do the correct accounting, we need to mark a page BP> to indicate if we reserved a block or not. One way to do this, BP> to use page->private to indicate this. But then, all the generic BP> routines will fail - since they assume that page->private represents BP> bufferheads. So we need a better way to do this. you can introduce one more bit to page->flags BP> 3) We need add hooks into filesystem specific calls from these BP> generic routines to handle "journaling mode" requirements BP> (for ext3 and may be others). nobody uses journaling mode except ext3