From: Jens Axboe <axboe@suse.de>
To: Shaun <delius@progsoc.uts.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Disk Performance Measurements
Date: Thu, 3 May 2001 12:46:47 +0200 [thread overview]
Message-ID: <20010503124647.F16507@suse.de> (raw)
In-Reply-To: <20010502124445.J25336@suse.de> <Pine.LNX.4.21.0105030750410.10591-100000@ftoomsh.progsoc.uts.edu.au>
In-Reply-To: <Pine.LNX.4.21.0105030750410.10591-100000@ftoomsh.progsoc.uts.edu.au>; from delius@progsoc.uts.edu.au on Thu, May 03, 2001 at 07:59:53AM +1000
On Thu, May 03 2001, Shaun wrote:
> Again, this isn't the case in the 2.2.16 kernel I'm working with. Each
> call to make_request() causes pgin/pgout to be incremented, since these
> requests can be of different sizes (even for the same disk) I can't see
> how a kb value can be deduced.
Check if the latest 2.2 is correct then, 2.4 is.
> Just as a question though, a disk/partition doesn't need to have a
> filesystem on it, so why is the "correct_size" for a buffer request on the
> block device defined based on a filesystem block system?
It's not, but the fs may set the block size (ext2 does).
--
Jens Axboe
prev parent reply other threads:[~2001-05-03 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 6:31 Disk Performance Measurements Shaun
2001-05-02 10:44 ` Jens Axboe
2001-05-02 21:59 ` Shaun
2001-05-03 10:46 ` 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=20010503124647.F16507@suse.de \
--to=axboe@suse.de \
--cc=delius@progsoc.uts.edu.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox