From: Christoph Hellwig <hch@lst.de>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH, RFC] map multiple blocks at a time in mpage_readpage(s)
Date: Wed, 5 Oct 2005 09:14:08 +0200 [thread overview]
Message-ID: <20051005071408.GB27081@lst.de> (raw)
In-Reply-To: <1128467744.4754.47.camel@dyn9047017102.beaverton.ibm.com>
On Tue, Oct 04, 2005 at 04:15:43PM -0700, Badari Pulavarty wrote:
> Do you really want mpage_readpage()/mpage_readpages() to take
> get_blocks() and get_block() to take as arguments ? Or it just
> a initial version and you have grand plans to clean it up ?
> Me & Suparna did a version which needed only get_blocks()
> few months ago. I can try to dig it up, if you like.
I don't see how to get rid of it easily. It's need for the confused
case that calls block_read_full_page, which needs a get_block()
callback. Adding a failback_writepage callback would be a tad nicer
but not really solve the general issue.
> In fact, we want to do the same thing for writepages() also - so
> that the filesystem can do the block allocation in a single shot.
> (as part of delayed allocation).
I'm doing something like that internally for XFS right now. Due to
thinks like delayed allocations, unwritten extents and probing ahead
unmapped blocks (for the mmap write case) we can't use the common
code currently - but I plan to get it closer to it so eventually we
could make the generic code handle all that. It's just a long term
TODO list item, not a short term one.
next prev parent reply other threads:[~2005-10-05 7:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 19:42 [PATCH, RFC] map multiple blocks at a time in mpage_readpage(s) Christoph Hellwig
2005-10-04 22:05 ` Dave Kleikamp
2005-10-04 23:15 ` Badari Pulavarty
2005-10-05 7:14 ` Christoph Hellwig [this message]
2005-10-07 22:13 ` Badari Pulavarty
2005-10-05 6:04 ` Nikita Danilov
2005-10-05 7:10 ` Christoph Hellwig
2005-10-05 16:11 ` Suparna Bhattacharya
2005-10-19 11:56 ` Christoph Hellwig
2005-10-19 15:07 ` Dave Kleikamp
2005-10-20 22:06 ` Andrew Morton
2005-10-21 6:18 ` Suparna Bhattacharya
2005-10-21 12:53 ` Dave Kleikamp
2005-10-21 14:16 ` Jörn Engel
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=20051005071408.GB27081@lst.de \
--to=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pbadari@gmail.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).