public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] blkstat
Date: Mon, 13 Jun 2005 20:05:38 +1000	[thread overview]
Message-ID: <200506132005.40846.kernel@kolivas.org> (raw)
In-Reply-To: <42AD59A9.3030404@yahoo.com.au>

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

On Mon, 13 Jun 2005 20:02, Nick Piggin wrote:
> Con Kolivas wrote:
> > On Mon, 13 Jun 2005 19:46, Nick Piggin wrote:
> >>Oh, and before I go further, does anyone know of any program
> >>or statistic that allows the same functionality? Any comments?
> >
> > Would something like iostat give similar results?
>
> 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.

> You can kind of guess if you take into account the seeks,
> and the throughput, but you're still missing things like
> head position (eg. changes throughput), settle time and
> rotational latency, and lots of other stuff.
>
> Thanks,
> Nick
>
> Also, BTW. the way I have done the kernel patch make a
> device show 100% utilisation even if it is not doing anything
> but waiting for a plug, or an anticipatory scheduler. This
> is basically all the end user wants to know, although for
> development purposes it may be interesting to know the other
> metric too.

That sounds quite useful.

Cheers,
Con

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-06-13 10:06 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 [this message]
2005-06-13 10:19       ` Nick Piggin
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=200506132005.40846.kernel@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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