Re: Trapping Block I/O

[Fawad Lateef]

On 9/23/05, Jens Axboe <axboe@xxxxxxx> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/