From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] blkstat
Date: Mon, 13 Jun 2005 20:19:50 +1000 [thread overview]
Message-ID: <42AD5DC6.6090205@yahoo.com.au> (raw)
In-Reply-To: <200506132005.40846.kernel@kolivas.org>
Con Kolivas wrote:
> On Mon, 13 Jun 2005 20:02, Nick Piggin wrote:
>
>>The problem with that is that it does not give you a % idle
>>figure on the block device, so you basically can't see if
>>the device is becoming a bottleneck.
>
>
> I've often wondered how iostat gives a %busy figure and whether this
> translated accurately without further info from the kernel.
>
>
Oh, it does havea "%util" in its extended stats. Sorry I missed
that so you might be right.
Hmm, so I guess it uses io_ticks and that does appear to give
the valid measure. I'll have a think about that - perhaps there
is still a place for the split read/write statistics I'm using...
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-06-13 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 9:46 [RFC] blkstat Nick Piggin
2005-06-13 9:54 ` Con Kolivas
2005-06-13 10:02 ` Nick Piggin
2005-06-13 10:05 ` Con Kolivas
2005-06-13 10:19 ` Nick Piggin [this message]
2005-06-13 11:21 ` Andi Kleen
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=42AD5DC6.6090205@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=kernel@kolivas.org \
--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