From: Jens Axboe <jens.axboe@oracle.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [BTT PATCH] Major revamping (ver 2.0)
Date: Mon, 10 Sep 2007 16:39:24 +0000 [thread overview]
Message-ID: <20070910163924.GL6892@kernel.dk> (raw)
In-Reply-To: <46E33802.9040209@hp.com>
On Sat, Sep 08 2007, Alan D. Brunelle wrote:
> After a lot of fighting with maintaining a tree-styled design (each trace
> having it's own node), it was just getting too cumbersome to work in all
> circumstances. Taking a clue from blkparse itself, I decided to just keep
> track of IOs at queue time, and updating fields based upon later traces.
>
> The attached (large) patch works much faster, handles larger test cases
> with less failures, and is managing some pretty large jobs I'm working on
> (large Oracle-based DB analysis - 32-way box w/ lots of storage).
>
> I've also added a Q2Q seek distance feature - it's come in handy when
> comparing results of IO scheduler choice: We can see what the incoming IO
> seek distances are (at queue time), and then see how the scheduler itself
> manages things (via merges & sorting) by looking at D2D seek distances
> generated.
>
> As noted in the subject, I arbitrarily bumped this to version 2.00 as the
> innards are so different. The documentation (btt/doc/btt.tex) has been
> updated to reflect some minor output changes. I also fixed a bug dealing
> with process name notification: there was a problem that if a new PID came
> up with a name that was previously seen, btt wouldn't keep track of it
> right. [When running with Oracle, a lot of processes have the same name but
> different PIDs of course.]
Applied (the 2nd full variant).
--
Jens Axboe
prev parent reply other threads:[~2007-09-10 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 0:02 [BTT PATCH] Major revamping (ver 2.0) Alan D. Brunelle
2007-09-10 16:39 ` Jens Axboe [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=20070910163924.GL6892@kernel.dk \
--to=jens.axboe@oracle.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).