[ltt-dev] [PATCH] add tracepoints to track change in napi states on network receive

[nhorman@tuxdriver.com (Neil Horman)]

On Wed, Dec 03, 2008 at 01:21:33PM -0500, Mathieu Desnoyers wrote:
> * Mathieu Desnoyers (compudj at krystal.dyndns.org) wrote:
> > * Neil Horman (nhorman at tuxdriver.com) wrote:
> > > On Wed, Dec 03, 2008 at 12:25:07PM -0500, Mathieu Desnoyers wrote:
> > > > Almost there :)
> > > > 
> > > > There is a extra whitespace above,
> > > > 
> > > > and also  "schedule napi_struct" should probably be changed into
> > > > napi_struct only, this removes the whitespace and duplicated information
> > > > (I guess we know that given we are in event net_napi_schedule, this will
> > > > have something to do with schedule...). Same applies to trace_mark_tp
> > > > below.
> > > > 
> > > > Thanks,
> > > > 
> > > > Mathieu
> > > 
> > > 
> > > Sure, here you go, new patch
> > > 
> > > Patch to trace napi states for various net devices and their napi instances.
> > > Traces scheduling, servicing and completion of a napi poll request.
> > > 
> > > Regards
> > > Neil
> > > 
> > > Signed-off-by: Neil Horman <nhorman at tuxdriver.com>
> > > 
> > 
> > Actually I notice that you used the old "DEFINE_TRACE" tracepoint API.
> 
> The patch has been edited and folded into 
> lttng-instrumentation-net.patch
> lttng-instrumentation-net-tracepoints-probes.patch
> 
Thanks!
Neil


-- 
/****************************************************
 * Neil Horman <nhorman at tuxdriver.com>
 * Software Engineer, Red Hat
 ****************************************************/