From: "Alan D. Brunelle" <alan.brunelle@hp.com>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: axboe@suse.de, systemtap@sources.redhat.com,
linux-btrace@vger.kernel.org
Subject: Re: [blktrace kernel patch] Separate out non-blktrace-specific code
Date: Wed, 11 Oct 2006 15:27:00 -0000 [thread overview]
Message-ID: <452D0D30.8050405@hp.com> (raw)
In-Reply-To: <17702.34529.84263.377316@tut.ibm.com>
Tom Zanussi wrote:
> Tom Zanussi writes:
> > This patch moves the non-block-specific code out of the core blktrace
> > kernel code and moves it into a separate utt.* files, so that anyone
> > can use it for generic tracing. It also adds a config option,
> > CONFIG_UTT, and hooks up the remaining code in blktrace.c to use it.
> > The accompanying userspace patch does the same thing for the userspace
> > tools.
> >
>
> I should have mentioned that the kernel patch was against a recent git
> kernel, and doesn't apply cleanly to a 2.6.18 stable kernel. Here's a
> patch against 2.6.18 stable. I've only had time to compile-test it -
> no time right now to do anything more, since I'm almost out the
> door - hopefully it works...
>
> Tom
>
>
FYI: I was able to patch a 2.6.18-based kernel (with this patch) &
latest blktrace sources, and able to successfully capture traces and
process them with UTT in place. This seems to work just fine for me.
Alan
PS. Dual-Opteron w/ U320 SCSI disk used for tracing...
prev parent reply other threads:[~2006-10-11 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 23:30 Tom Zanussi
2006-10-06 16:39 ` Tom Zanussi
2006-10-11 15:27 ` 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=452D0D30.8050405@hp.com \
--to=alan.brunelle@hp.com \
--cc=axboe@suse.de \
--cc=linux-btrace@vger.kernel.org \
--cc=systemtap@sources.redhat.com \
--cc=zanussi@us.ibm.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).