From: Martin Peschke <mp3@de.ibm.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [Patch 0/3] driver data: blktrace pass-through support
Date: Wed, 16 Jul 2008 15:08:04 +0000 [thread overview]
Message-ID: <1216220884.26621.119.camel@kitka.ibm.com> (raw)
In-Reply-To: <1216207494.26621.82.camel@kitka.ibm.com>
On Wed, 2008-07-16 at 10:47 -0400, Alan D. Brunelle wrote:
> Hm, again, if the blktrace | blkiomon (direct, no blkparse) is how you
> do things,
no, it's blktrace | blkparse | blkiomon
Isn't blkparse needed to sort all those per-CPU traces by time?
I want this feature.
> I would think that it would /not/ take all that much
> processing power to parse character strings.
Anyway, it's more expensive.
> (I've heard that IBM makes some pretty fast processors... :-) )
Sure. But we don't make our money from wasting their CPU power :-)
next prev parent reply other threads:[~2008-07-16 15:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 11:24 [Patch 0/3] driver data: blktrace pass-through support for device Martin Peschke
2008-07-16 14:22 ` Alan D. Brunelle
2008-07-16 14:41 ` [Patch 0/3] driver data: blktrace pass-through support for Martin Peschke
2008-07-16 14:47 ` [Patch 0/3] driver data: blktrace pass-through support for device Alan D. Brunelle
2008-07-16 15:08 ` Martin Peschke [this message]
2008-07-16 15:15 ` Alan D. Brunelle
2008-07-16 15:43 ` [Patch 0/3] driver data: blktrace pass-through Martin Peschke
2008-07-17 12:17 ` [Patch 0/3] driver data: blktrace pass-through support for Martin Peschke
2008-07-17 12:27 ` [Patch 0/3] driver data: blktrace pass-through support for device Alan D. Brunelle
2008-10-05 13:07 ` Martin Peschke
2008-10-15 11:35 ` [Patch 0/3] driver data: blktrace pass-through support for 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=1216220884.26621.119.camel@kitka.ibm.com \
--to=mp3@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).