Re: [patch 4/4] Port of blktrace to the Linux Kernel Markers.

* Steven Rostedt ([EMAIL PROTECTED]) wrote: > On Tue, Sep 18, 2007 at 05:13:28PM -0400, Mathieu Desnoyers wrote: > > +void blk_probe_disarm(void) > > +{ > > + int i, err; > > + > > + for (i = 0; i < ARRAY_SIZE(probe_array); i++) { > > + err = marker_disarm(probe_array[i].name); > > +

Re: [patch 4/4] Port of blktrace to the Linux Kernel Markers.

On Tue, Sep 18, 2007 at 05:13:28PM -0400, Mathieu Desnoyers wrote: > +void blk_probe_disarm(void) > +{ > + int i, err; > + > + for (i = 0; i < ARRAY_SIZE(probe_array); i++) { > + err = marker_disarm(probe_array[i].name); > + BUG_ON(err); > + err = IS_ERR(

[patch 4/4] Port of blktrace to the Linux Kernel Markers.

Here is the first stage of a port of blktrace to the Linux Kernel Markers. The advantage of this port is that it minimizes the impact on the running when blktrace is not active. A few remarks : this patch has the positive effect of removing some code from the block io tracing hot paths, minimizing

[patch 4/4] Port of blktrace to the Linux Kernel Markers.

Here is the first stage of a port of blktrace to the Linux Kernel Markers. The advantage of this port is that it minimizes the impact on the running when blktrace is not active. A few remarks : this patch has the positive effect of removing some code from the block io tracing hot paths, minimizing

Re: [patch 4/4] Port of blktrace to the Linux Kernel Markers.

* Christoph Hellwig ([EMAIL PROTECTED]) wrote: > On Mon, Aug 27, 2007 at 12:05:44PM -0400, Mathieu Desnoyers wrote: > > Here is the first stage of a port of blktrace to the Linux Kernel Markers. > > The > > advantage of this port is that it minimizes the impact on the running when > > blktrace is

Re: [patch 4/4] Port of blktrace to the Linux Kernel Markers.

On Mon, Aug 27, 2007 at 12:05:44PM -0400, Mathieu Desnoyers wrote: > Here is the first stage of a port of blktrace to the Linux Kernel Markers. The > advantage of this port is that it minimizes the impact on the running when > blktrace is not active. > > A few remarks : this patch has the positive

[patch 4/4] Port of blktrace to the Linux Kernel Markers.

Here is the first stage of a port of blktrace to the Linux Kernel Markers. The advantage of this port is that it minimizes the impact on the running when blktrace is not active. A few remarks : this patch has the positive effect of removing some code from the block io tracing hot paths, minimizing

[patch 4/4] Port of blktrace to the Linux Kernel Markers.

Here is the first stage of a port of blktrace to the Linux Kernel Markers. The advantage of this port is that it minimizes the impact on the running when blktrace is not active. A few remarks : this patch has the positive effect of removing some code from the block io tracing hot paths, minimizing

[patch 4/4] Port of blktrace to the Linux Kernel Markers.

Here is the first stage of a port of blktrace to the Linux Kernel Markers. The advantage of this port is that it minimizes the impact on the running when blktrace is not active. A few remarks : this patch has the positive effect of removing some code from the block io tracing hot paths, minimizing

[patch 4/4] Port of blktrace to the Linux Kernel Markers.

Here is the first stage of a port of blktrace to the Linux Kernel Markers. The advantage of this port is that it minimizes the impact on the running when blktrace is not active. A few remarks : this patch has the positive effect of removing some code from the block io tracing hot paths, minimizing

[patch 4/4] Port of blktrace to the Linux Kernel Markers.

Here is a proof of concept patch, for demonstration purpose, of moving blktrace to the markers. A few remarks : this patch has the positive effect of removing some code from the block io tracing hot paths, minimizing the i-cache impact in a system where the io tracing is compiled in but inactive.