All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
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: Fri, 21 Oct 2005 11:48:40 +0530	[thread overview]
Message-ID: <20051021061840.GA3958@in.ibm.com> (raw)
In-Reply-To: <20051020150631.1f860552.akpm@osdl.org>

On Thu, Oct 20, 2005 at 03:06:31PM -0700, Andrew Morton wrote:
> Christoph Hellwig <hch@lst.de> wrote:
> >
> > On Tue, Oct 04, 2005 at 09:42:46PM +0200, Christoph Hellwig wrote:
> >  > This patch changes mpage_readpage/mpage_readpages to use a get_blocks
> >  > call that gets the disk mapping information for multiple blocks at the
> >  > same time, similar to the way direct I/O code works.  For extent based
> >  > filesystems like jfs, xfs or reiser4 this allows to reduce the overhead
> >  > of the allocator calls, which is especially nice when that codepath
> >  > is rather heavyweight (as it is for example in xfs).  For filesystems
> >  > that don't have an allocator that make use of it nothing changes.
> >  > 
> >  > I've tested this heavily on XFS with block size = page size and 512 byte
> >  > blocks, and it passes the XFS QA regression test suite fine.  I've done
> >  > some basic fsx testing on all the other affected filesystems.
> > 
> >  I think the patch should go into -mm after no one had serious objections.
> 
> It adds a bunch of complexity and overhead which will speed up a filesystem
> which few people use while slowing down the filesystems which most people
> use.
> 
> If/when we have an ext3 implementation of get_blocks() and some benchmarks
> which show it's worthwhile then OK.

We do already have this based on reservation based allocation (Mingming
posted the patches a while back). I think we need to combine the work we did
for mpage_writepages with the readpages work.

> 
> Could we please see the xfs benchmark results?
> 
> first_logical_block should have type sector_t.
> 
> Did you consider aggregating those nine args to do_mpage_readpage() into a
> struct, passing the address of that?

Regards
Suparna

> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India


  reply	other threads:[~2005-10-21  6:09 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
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 [this message]
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=20051021061840.GA3958@in.ibm.com \
    --to=suparna@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.