From: Mark Seger <Mark.Seger@hp.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, Alan Brunelle <Alan.Brunelle@hp.com>
Subject: Re: Accuracy of disk statistics IO counter
Date: Tue, 01 Aug 2006 15:30:40 -0400 [thread overview]
Message-ID: <44CFABE0.8020501@hp.com> (raw)
In-Reply-To: <20060729104232.GD13095@suse.de>
>>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.
>
>
I had problems getting blktrace going and posted a note to
linux-btrace@vger.kernel.org at Alan Brunelle's suggestion and he also
said he'd take a closer look at it himself. On the other hand he
pointed me to 'stap' and I was able to use it to get the details I was
looking for - SystemTAP really rocks for this type of analysis! As it
turns out my assumption about driver blocksize was wrong (sorry about
that). It turns out that the size of requests from the driver to the
disk is 160mb and so the I/O count was smaller than I had anticipated.
-mark
next prev parent reply other threads:[~2006-08-01 19:30 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
2006-08-01 19:30 ` Mark Seger [this message]
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=44CFABE0.8020501@hp.com \
--to=mark.seger@hp.com \
--cc=Alan.Brunelle@hp.com \
--cc=axboe@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox