From: Alex Tomas <alex@clusterfs.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Martin Jambor <jamborm@gmail.com>, linux-fsdevel@vger.kernel.org
Subject: Re: Lazy block allocation and block_prepare_write?
Date: Tue, 19 Apr 2005 14:10:13 +0400 [thread overview]
Message-ID: <m3y8bfcc1m.fsf@bzzz.home.net> (raw)
In-Reply-To: <42647484.5040208@us.ibm.com> (Badari Pulavarty's message of "Mon, 18 Apr 2005 20:01:24 -0700")
>>>>> 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
next prev parent reply other threads:[~2005-04-19 10:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 0:54 Lazy block allocation and block_prepare_write? Martin Jambor
2005-04-19 3:01 ` Badari Pulavarty
2005-04-19 10:10 ` Alex Tomas [this message]
2005-04-19 14:48 ` Badari Pulavarty
2005-04-19 15:04 ` Alex Tomas
2005-04-19 15:00 ` Badari Pulavarty
2005-04-19 15:20 ` Alex Tomas
2005-04-19 11:22 ` Nikita Danilov
2005-04-19 14:46 ` Badari Pulavarty
2005-04-19 15:55 ` Nikita Danilov
2005-04-19 16:06 ` Alex Tomas
2005-04-19 16:59 ` Badari Pulavarty
2005-04-19 17:08 ` Mingming Cao
2005-04-19 18:45 ` Nikita Danilov
2005-04-20 0:00 ` Bryan Henderson
2005-04-19 20:41 ` Martin Jambor
2005-04-20 14:52 ` Badari Pulavarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3y8bfcc1m.fsf@bzzz.home.net \
--to=alex@clusterfs.com \
--cc=jamborm@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).