From: "Alan D. Brunelle" <alan.brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: Re: blkparse not displaying all events when tracing >1 devices?
Date: Thu, 16 Sep 2010 11:54:05 +0000 [thread overview]
Message-ID: <4C92055D.5070201@hp.com> (raw)
In-Reply-To: <4C9148BF.1000306@netezza.com>
Hm, well, the problem is (I believe) that with the "-o" option just
isn't designed to work with multiple devices.
Brett: The simplest thing to do for your example would be:
# blktrace /dev/sdbk /dev/sdam
...
# blkparse -q sdbk sdam
Basically, listing each device used on the blkparse line. [That's how I
(and presumably everyone else) has always done it.]
The technical reason why "-o" doesn't work with multiple devices is
because we use multiple threads of execution - one per device/CPU pair -
and each of them opens a file named "<prefix>.blktrace.<cpu>". With the
"-o" all of the "<prefix>" values are the same - so multiple threads
open the same file and try to do output. Not good. Without the "-o" we
get unique files named: "<device>.blktrace.<cpu>" - as the tuple
(<device>,<cpu>) is unique.
I suppose we could change the definition of "-o" to be:
"<prefix>.<device>.blktrace.<cpu>" - but I don't know what else this
would break. So, I think what I'll do is update the documentation to
just note that "-o" doesn't work with multiple devices.
Regards,
Alan
prev parent reply other threads:[~2010-09-16 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 22:29 blkparse not displaying all events when tracing >1 devices? Brett Russ
2010-09-16 11:54 ` Alan D. Brunelle [this message]
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=4C92055D.5070201@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).