From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Re: question about btt and blkparse
Date: Tue, 21 Apr 2009 10:44:30 +0000 [thread overview]
Message-ID: <49EDA38E.8070305@hp.com> (raw)
Hello Kejian -
The proper work-flow is as follows:
(1) blktrace -d /dev/sda
(2) blkparse -i sda.blktrace.0 -o o.parse -d bp.bin
(3) btt -i bp.bin -p o.btt
'btt' runs on the binary output from blkparse (the '-d bp.bin' in step
2) - not directly from the x.blktrace.y files generated by blktrace.
When you do it in this order, you get the correct stamps from btt:
8,0 : 0.000281229 Q 3368431+8
0.000282543 M 3368431+8
0.000387733 D 3368407+112
0.011695204 C 3368407+112
which can be found in o.parse:
8,0 0 13 0.000281229 461 Q W 3368431 + 8 [kjournald]
8,0 0 14 0.000282543 461 M W 3368431 + 8 [kjournald]
...
8,0 0 46 0.000387733 461 D W 3368407 + 112 [kjournald]
8,0 0 47 0.011695204 0 C W 3368407 + 112 [0]
Regards,
Alan
reply other threads:[~2009-04-21 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49EDA38E.8070305@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 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).