From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Re: the difference between btt and blkparse
Date: Mon, 01 Mar 2010 19:20:32 +0000 [thread overview]
Message-ID: <1267471232.2961.11.camel@cail> (raw)
In-Reply-To: <398d69301003010326n5654ea69y4cffa4e7439d3800@mail.gmail.com>
On Mon, 2010-03-01 at 19:26 +0800, Xuekun Hu wrote:
> Hi, Guys
>
> >From the doc, the standard work-flow for btt is to handle the binary
> output from "blkparse -d". I found btt can also directly handle the
> raw trace file generated by blktrace. However I found the two results
> are not match.
'btt' is intended only to be run w/ the output from blkparse -d : the
fact that "it kind of works" with straight blktrace output only means
that the results will be "kind of right". :-)
Regards,
Alan
next prev parent reply other threads:[~2010-03-01 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 11:26 the difference between btt and blkparse Xuekun Hu
2010-03-01 19:20 ` Alan D. Brunelle [this message]
2010-03-02 3:44 ` Xuekun Hu
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=1267471232.2961.11.camel@cail \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox