From: "M. Edward (Ed) Borasky" <znmeb@cesmail.net>
To: linux-btrace@vger.kernel.org
Subject: Documentation on the binary file format?
Date: Thu, 29 Jan 2009 18:24:35 +0000 [thread overview]
Message-ID: <4981F463.1050905@cesmail.net> (raw)
Is there some documentation on the binary file format out of "blktrace"?
I'm interested in writing some post-processing routines that extend what
"blkparse" and "btt" do, and there is a substantial disk space hit if I
generate the "blkparse" output and post-process that. I'm also
considering a network server that takes the binary data from a
"blktrace" client and does the analysis "on the fly", rather than saving
off a binary trace.
A side question ... how likely are changes in the binary format? The
language(s) I want to use -- Perl and/or Ruby -- are pretty flexible at
re-factoring to match format changes, but I'd like to have a clue on how
much maintenance activity I'm taking on.
--
M. Edward (Ed) Borasky
I've never met a happy clam. In fact, most of them were pretty steamed.
next reply other threads:[~2009-01-29 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 18:24 M. Edward (Ed) Borasky [this message]
2009-01-30 7:39 ` Documentation on the binary file format? 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=4981F463.1050905@cesmail.net \
--to=znmeb@cesmail.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.