From: Andrew Morton <akpm@osdl.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, pbadari@us.ibm.com
Subject: Re: [PATCH 0/4] map multiple blocks in get_block() and mpage_readpages()
Date: Wed, 1 Mar 2006 17:52:30 -0800 [thread overview]
Message-ID: <20060301175230.4b96e9ad.akpm@osdl.org> (raw)
In-Reply-To: <1141075239.10542.19.camel@dyn9047017100.beaverton.ibm.com>
Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
> I noticed decent improvements (reduced sys time) on JFS, XFS and ext3.
> (on simple "dd" read tests).
>
> (rc3.mm1) (rc3.mm1 + patches)
> real 0m18.814s 0m18.482s
> user 0m0.000s 0m0.004s
> sys 0m3.240s 0m2.912s
With which filesystem? XFS and JFS implement a larger-than-b_size
->get_block, but ext3 doesn't. I'd expect ext3 system time to increase a
bit, if anything?
next prev parent reply other threads:[~2006-03-02 1:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 21:20 [PATCH 0/4] map multiple blocks in get_block() and mpage_readpages() Badari Pulavarty
2006-02-27 21:22 ` [PATCH 1/4] change buffer_head.b_size to size_t Badari Pulavarty
2006-03-02 1:51 ` Andrew Morton
2006-03-02 1:51 ` Andrew Morton
2006-03-02 2:22 ` Nathan Scott
2006-03-02 2:56 ` Andrew Morton
2006-03-06 19:54 ` Tim Pepper
2006-02-27 21:23 ` [PATCH 2/4] pass b_size to ->get_block() Badari Pulavarty
2006-03-02 1:52 ` Andrew Morton
2006-03-03 17:17 ` Badari Pulavarty
2006-02-27 21:24 ` [PATCH 3/4] map multiple blocks for mpage_readpages() Badari Pulavarty
2006-03-02 4:45 ` Andrew Morton
2006-03-03 16:51 ` Badari Pulavarty
2006-02-27 21:24 ` [PATCH 4/4] remove ->get_blocks() support Badari Pulavarty
2006-03-02 1:52 ` Andrew Morton [this message]
2006-03-03 17:05 ` [PATCH 0/4] map multiple blocks in get_block() and mpage_readpages() Badari Pulavarty
2006-03-03 20:32 ` Andrew Morton
2006-03-03 21:54 ` 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=20060301175230.4b96e9ad.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@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