All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Kurt Garloff <garloff@suse.de>,
	Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: read perf improved by mounting ext2?
Date: Tue, 24 Apr 2001 11:14:02 +0200	[thread overview]
Message-ID: <20010424111402.E9357@suse.de> (raw)
In-Reply-To: <20010424013150.A6892@garloff.etpnet.phys.tue.nl> <20010424105858.C9357@suse.de> <20010424110532.E12624@garloff.etpnet.phys.tue.nl>
In-Reply-To: <20010424110532.E12624@garloff.etpnet.phys.tue.nl>; from garloff@suse.de on Tue, Apr 24, 2001 at 11:05:32AM +0200

On Tue, Apr 24 2001, Kurt Garloff wrote:
> > You wouldn't happen to have 4kB ext2 filesystems on those?
> 
> Sure I do.
> 
> > When ext2 mounts, it sets the soft blocksize to that then, I would expect
> > this to give at least some benefit over using 1kB blocks (as your IDE
> > partition otherwise would have).
> 
> Why? Are the request sizes larger this way? This would mean that the
> overhead is very significant, turning a max of 26MB/s into 16MB/s!

Because you'll be doing I/O on 4kB entries at least, and the overhead of
merging a 128kB request into the queue is much smaller this way. But
yes, 16 -> 26 seems quite a large win, I wouldn't expect this much
(unless you get no merging in any of the cases, then I suspect the 4kB
would be an even bigger win)

> If so, shouldn't we try to get the same effect also for the whole disk or
> other filesystems? Most notably reiser?

I would expect reiser to do the same. Setting the soft block size higher
is not required though, users are free to submit 4kB buffer heads even
for devices that have 1kB set. By default, it doesn't happen though.

-- 
Jens Axboe


      reply	other threads:[~2001-04-24  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 23:31 read perf improved by mounting ext2? Kurt Garloff
2001-04-24  8:58 ` Jens Axboe
2001-04-24  9:05   ` Kurt Garloff
2001-04-24  9:14     ` Jens Axboe [this message]

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=20010424111402.E9357@suse.de \
    --to=axboe@suse.de \
    --cc=garloff@suse.de \
    --cc=linux-kernel@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.