From mboxrd@z Thu Jan 1 00:00:00 1970 From: nhorman@tuxdriver.com (Neil Horman) Date: Wed, 3 Dec 2008 14:26:06 -0500 Subject: [ltt-dev] [PATCH] add tracepoints to track change in napi states on network receive In-Reply-To: <20081203182133.GB6794@Krystal> References: <20081202195129.GA30042@hmsreliant.think-freely.org> <20081202200150.GA27282@Krystal> <20081203160134.GA6549@hmsreliant.think-freely.org> <20081203172507.GA4471@Krystal> <20081203174500.GB6549@hmsreliant.think-freely.org> <20081203181105.GA6794@Krystal> <20081203182133.GB6794@Krystal> Message-ID: <20081203192606.GC6549@hmsreliant.think-freely.org> 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 > > > > > > > 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 * Software Engineer, Red Hat ****************************************************/