From: Phillip Susi <psusi@ubuntu.com>
To: linux-btrace@vger.kernel.org
Subject: Re: Events out of order
Date: Wed, 31 Dec 2014 15:09:22 +0000 [thread overview]
Message-ID: <54A411A2.1060605@ubuntu.com> (raw)
In-Reply-To: <54A355D2.5060704@ubuntu.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/31/2014 9:58 AM, Chris Mason wrote:
> It's been a while since I looked at this, but looks like blkparse
> has a pipeline mode and a more exact mode. In pipeline mode, it's
> really trying to get data to the screen quickly and without using a
> huge amount of resources. In order to put things in order, it
> would need to buffer the entire stream before outputting anything.
> So instead it works in chunks, which is what you're seeing.
Makes sense; it would be nice if the man page mentioned this drawback.
> It enables pipeline mode when the input file from -i is a pipe.
> You'll get better results if you allow blktrace to output into a
> collection of files and pass the prefix to blkparse.
>
> instead of blktrace -o - use blktrace -o prefix ; blkparse -i
> prefix
>
> For multiple devices, iowatcher uses a directory to store all of
> them, which is easier.
>
> If you really want a single file result, take the per-cpu files
> from blktrace, run them through blkparse and add -d dumpfile, which
> will sort and pack all the results into a single binary file. It's
> compressable and you can then delete all the per-cpu files.
Thanks; I thought I read something like that at one point but couldn't
find it in the man page last night.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQEcBAEBAgAGBQJUpBGiAAoJENRVrw2cjl5R5EcH/AoLTOH7JzM62//2/V4Ely5U
OTnDkD4Aq2ydS7SQ3otidPnCJ46zCwlACZxJHknxM3RkLkXQUsqjXJ9J0l6Bitav
u06jZHyr07d9ysRexeLMpPJsdzFzrY41G8ZjTNFJJBGgNv/y8zlqT1gXZ8QjJYjw
XSsBVy+8D7yPJRAwX7eXbrfwKRfe16N+ujQC1DXnVOVKDKeP1inG7vRDdUuzjciA
63Gf8Kdk8E4Rlh9zyR8QWSB15Tp92/bLIeoJjZIoqsLlrRFoizREyPLpVXhg3Zhn
M6C+/H9cm+wB2KDiDESLm7uNyokYeAyQGbesj7/WTj/Lccv29drFMF9cCYLk4nk¿Zz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-31 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 1:48 Events out of order Phillip Susi
2014-12-31 1:51 ` Phillip Susi
2014-12-31 1:53 ` Alireza Haghdoost
2014-12-31 3:23 ` Phillip Susi
2014-12-31 4:29 ` Alireza Haghdoost
2014-12-31 14:36 ` Phillip Susi
2014-12-31 14:58 ` Chris Mason
2014-12-31 15:09 ` Phillip Susi [this message]
2014-12-31 15:19 ` Jens Axboe
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=54A411A2.1060605@ubuntu.com \
--to=psusi@ubuntu.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).