From: Fawad Lateef <fawadlateef@gmail.com>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Trapping Block I/O
Date: Fri, 23 Sep 2005 23:52:37 +0500 [thread overview]
Message-ID: <1e62d1370509231152ac90f99@mail.gmail.com> (raw)
In-Reply-To: <20050923184342.GJ22655@suse.de>
On 9/23/05, Jens Axboe <axboe@suse.de> wrote:
> > Ya, I looked at it and its looking very good tool to tracing block I/O
> > layer, but this tracing requires recompilation of the kernel and have
> > to use on kernel directly from kernel.org but its not a big deal, I
> > hope it will get into the main kernel soon ....
>
> That is true, I plan on submitting it for 2.6.15. The goal was to get
> relayfs pushed in first and that did happen for 2.6.14.
>
That will be nice ....
>
> There are certainly a lot of ways to get the data out to user space, by
> far the bulk of the code is in the monitoring application. blktrace
> should be pretty fast though, one of the goals was to make sure it would
> be very light weight on the kernel side (which it is) and very fast on
> getting the data out (also achieved, relayfs works very well). The
> xprobe approach does have certain advantages, the main one being that
> you can easily modify it.
>
I will test/use it soon and will let you know if find any bug/problem :)
--
Fawad Lateef
next prev parent reply other threads:[~2005-09-23 18:52 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
2005-09-23 18:30 ` Fawad Lateef
2005-09-23 18:43 ` Jens Axboe
2005-09-23 18:52 ` Fawad Lateef [this message]
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=1e62d1370509231152ac90f99@mail.gmail.com \
--to=fawadlateef@gmail.com \
--cc=axboe@suse.de \
--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 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).