From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: linux-btrace@vger.kernel.org
Subject: [RFC] Implement simple messages in blktrace stream
Date: Fri, 23 May 2008 20:35:15 +0000 [thread overview]
Message-ID: <48372A83.9040204@hp.com> (raw)
The following two patches (kernel + application) would allow one to
annotate parts of the blktrace stream w/ simple messages.
I've included a sample one for elevator switches:
8,16 1 813055 20.259000000 4692 I R 3088320 + 8 [dd]
8,16 1 813056 20.259000000 4692 Q R 3088328 + 8 [dd]
8,16 1 20.259000000 0 m N elv switch: deadline
8,16 1 813057 20.259000000 4692 G R 3088328 + 8 [dd]
8,16 1 813058 20.259000000 4692 I R 3088328 + 8 [dd]
These patches are a bit rough (but compile, and appear to work ok so
far). In particular, I'd break the kernel patch into a blktrace addition
and an elevator switch addition, plus the application patch would need
documentation updates.
My nefarious ultimate goal would be to add in the ability for user-level
insertions for (e.g.):
1. Start blktrace
2. Do some stuff...
3. Insert a tag "switching to other stuff"
4. Do other stuff
5. Insert a tag "switching to yet other stuff"
6. Do yet other stuff
This way you could study different parts of the resultant traces using
the tags to separate them time-wise. [For now, I'd just switch
schedulers back and forth to see the separators.)
Looking for comments (hence the RFC).
Alan D. Brunelle
HP OSLO S&P
next reply other threads:[~2008-05-23 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 20:35 Alan D. Brunelle [this message]
2008-05-25 23:59 ` [RFC] Implement simple messages in blktrace stream Carl Henrik Lunde
2008-05-26 7:30 ` Jens Axboe
2008-05-26 17:05 ` Jens Axboe
2008-05-26 18:45 ` Carl Henrik Lunde
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=48372A83.9040204@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 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.