From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [Patch 2/2] blkiomon: I/O monitor
Date: Wed, 16 Jul 2008 13:37:15 +0000 [thread overview]
Message-ID: <487DF98B.9020708@hp.com> (raw)
In-Reply-To: <1216207425.26621.79.camel@kitka.ibm.com>
Martin Peschke wrote:
> blkiomon periodically generates per device request size and request latency
> statistics from blktrace data. It provides histograms as well as data that
> can be used to calculate min, max, average and variance. For this purpose,
> it consumes D and C traces read from stdin.
>
> There are options for binary output and human-readable output to files and
> stdout. Output to a message queue is supported as well.
>
> # blktrace /dev/sdw -a issue -a complete -w 3000 -o - \
> | blkparse -i - -O -d - | blkiomon -I 10 -h -
>
> device: 65,96 interval end: 1216044286134293
What units are 'interval end' displayed in?
> requests: read 521, write 34, bidir: 0
> sizes: min 4096, max 520192, sum 32059392, squ 4300285673472
> d2c: min 238, max 19274, sum 726186, squ 2428562090
Why not show the average? What is 'squ'?
> sizes histogram (in kB):
> 0 1 2 4 8 16 32 64
> 128 256 512 1024 2048 4096 8192 16384
> 0 0 0 64 17 144 71 117
> 97 42 3 0 0 0 0 0
These outputs are a bit hard to read - are they wrapped (from very, very
long lines), or is this how they are displayed? If the latter, why not
have some sort of MxN chart like:
0: 0 1: 0 2: 0 4: 64
8: 17 16:144 32: 71 64:117
128: 97 256: 42 512: 3 1024: 0
2048: 0 4096: 0 8192: 0 16384: 0
next prev parent reply other threads:[~2008-07-16 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 11:23 [Patch 2/2] blkiomon: I/O monitor Martin Peschke
2008-07-16 13:37 ` Alan D. Brunelle [this message]
2008-07-16 14:53 ` Martin Peschke
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=487DF98B.9020708@hp.com \
--to=alan.brunelle@hp.com \
--cc=linux-btrace@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.