From: Jens Axboe <axboe@suse.de>
To: Mark Seger <Mark.Seger@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Accuracy of disk statistics IO counter
Date: Sat, 29 Jul 2006 12:42:32 +0200 [thread overview]
Message-ID: <20060729104232.GD13095@suse.de> (raw)
In-Reply-To: <44CA3523.9020000@hp.com>
On Fri, Jul 28 2006, Mark Seger wrote:
> Awhile back I had suggested moving the place in the block driver logic
> where stats get updated to more accurately reflect what was happening at
> the time they were actually sent to the drivers and I believe they were
> indeed made in the 2.6.15 timeframe. I've recently started taking
> closer look at the numbers and while the sector counts look correct I'm
> not sure I'd agree with the number of I/Os being reported and believe
> they can be off by maybe 15% or more.
>
> Specifically, I wrote a 1GB file with a blocksize of 1MB, which would
> result in 1000 writes at the application level. What I believe then
> happens is that each write turns into 8 128KB requests to the driver,
> which should result in 8000 actual writes. Toss in metadata operations
> and who knows what else and the actual number should be a little
> higher. What I've see after repeating the tests a number of times on
> 2.6.16-27 is numbers ranging from 6800-7000 writes which feels like a
> big enough difference to at least point out.
Install http://brick.kernel.dk/snaps/blktrace-git-20060723022503.tar.gz
and blktrace your disk for the duration of the test and compare the io
numbers. Requires 2.6.17 or later, though.
--
Jens Axboe
next prev parent reply other threads:[~2006-07-29 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 16:02 Accuracy of disk statistics IO counter Mark Seger
2006-07-29 10:42 ` Jens Axboe [this message]
2006-08-01 19:30 ` Mark Seger
2006-08-01 19:39 ` Jens Axboe
2006-08-01 19:43 ` Mark Seger
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=20060729104232.GD13095@suse.de \
--to=axboe@suse.de \
--cc=Mark.Seger@hp.com \
--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