From: Jens Axboe <axboe@suse.de>
To: Fawad Lateef <fawadlateef@gmail.com>
Cc: Block Device <blockdevice@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Trapping Block I/O
Date: Fri, 23 Sep 2005 20:14:36 +0200 [thread overview]
Message-ID: <20050923181435.GI22655@suse.de> (raw)
In-Reply-To: <1e62d137050923111046d0b762@mail.gmail.com>
On Fri, Sep 23 2005, Fawad Lateef wrote:
> On 9/23/05, Jens Axboe <axboe@suse.de> wrote:
> > On Fri, Sep 23 2005, Fawad Lateef wrote:
> > > you created wrapper .... So by doing this you can easily monitor
> > > requests (similar to this approach is used in LVM/RAID) ......
> >
> > Or just use btrace, pull it from:
> >
> > git://brick.kernel.dk/data/git/blktrace.git
> >
>
> Thnx for telling about btrace .... I havn't tried/looked at it before !!!!
Well it's pretty new, so no wonder. But it should do everything you want
and lots more. There's a list for it here:
linux-btrace@vger.kernel.org
I'm a little pressed for time these days, but I'll do a proper announce
/ demo of all the features starting next week since it's basically
feature complete now.
If you don't use git, there are also snapshots available on kernel.org,
more precisely here:
kernel.org/pub/linux/kernel/people/axboe/blktrace/
but kernel.org is pretty slow these days, so pulling from the git repo
above is greatly recommended.
--
Jens Axboe
next prev parent reply other threads:[~2005-09-23 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 12:43 Trapping Block I/O Block Device
2005-09-23 17:38 ` Fawad Lateef
2005-09-23 18:04 ` Jens Axboe
2005-09-23 18:10 ` Fawad Lateef
2005-09-23 18:14 ` Jens Axboe [this message]
2005-09-23 18:30 ` Fawad Lateef
2005-09-23 18:43 ` Jens Axboe
2005-09-23 18:52 ` Fawad Lateef
2005-09-27 11:40 ` Block Device
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=20050923181435.GI22655@suse.de \
--to=axboe@suse.de \
--cc=blockdevice@gmail.com \
--cc=fawadlateef@gmail.com \
--cc=linux-kernel@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.