All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [Patch 0/2] blkiomon: I/O monitor based on blktrace data
Date: Wed, 16 Jul 2008 13:28:35 +0000	[thread overview]
Message-ID: <487DF783.7000602@hp.com> (raw)
In-Reply-To: <1216207358.26621.75.camel@kitka.ibm.com>

Martin Peschke wrote:
> In order to analyse I/O performance problems which could be reported by
> customers we want to provide a little monitoring tool. Primarily, we
> would like to be able look at a history of request size and request
> latency histograms per device.
> 
> The D and C traces provided by blktrace are exactly what we need for
> that purpose. So, running blktrace with appropriate filters (-a option)
> makes this approach feasible.
> 
> Patch 1/2 allows users to get binary output from blkparse on stdout.
> 
> Patch 2/2 contains blkiomon, an I/O monitoring tool, which reads
> blkparse data from stdin and which periodically writes I/O statistics.
> 
> I would like to contribute this little tool to the blktrace source tree.
> I think it would complement blkparse and btt quite well.
> 
> Martin

Hi Martin -

Is there some reason why you don't just parse the textual output from
blkparse itself? [I believe that's what Chris Mason does w/ his
seekwatcher for example.]

Alan

  reply	other threads:[~2008-07-16 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 11:22 [Patch 0/2] blkiomon: I/O monitor based on blktrace data Martin Peschke
2008-07-16 13:28 ` Alan D. Brunelle [this message]
2008-07-16 14:34 ` Martin Peschke
2008-07-16 14:43 ` Alan D. Brunelle
2008-07-16 15:15   ` 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=487DF783.7000602@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.