From: Jens Axboe <axboe@suse.de>
To: Mark Seger <Mark.Seger@hp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Fwd: Re: Patch for inconsistent recording of block device statistics]
Date: Mon, 31 Oct 2005 20:08:13 +0100 [thread overview]
Message-ID: <20051031190813.GC19267@suse.de> (raw)
In-Reply-To: <435E7A7B.3040806@hp.com>
On Tue, Oct 25 2005, Mark Seger wrote:
> yes, the patch worked. The general discussion was that the byte counter
> gets incremented when requests are queued, not when they're acted upon
> as is the case with the count of I/Os. As a result, the disk write
> numbers don't make any sense reporting impossibly high numbers (>100MB
> and as high as 450!) during some times and at other reporting zeros.
> The entire time, the I/O counts are happily showing what appear to be
> correct numbers. Here's a snapshot taken during a portion of a 2GB file
> file to /tmp.
I've applied my path to the for-linus git branch, I will push it for
2.6.15 as well. Thanks for reminding me!
--
Jens Axboe
prev parent reply other threads:[~2005-10-31 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 16:43 [Fwd: Re: Patch for inconsistent recording of block device statistics] Mark Seger
2005-10-25 6:40 ` Jens Axboe
2005-10-25 18:33 ` Mark Seger
2005-10-31 19:08 ` 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=20051031190813.GC19267@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