login
Header Space

 
 

Re: [patch 37/37] LTTng instrumentation net

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Pavel Emelyanov <xemul@...>
Cc: <akpm@...>, Ingo Molnar <mingo@...>, <linux-kernel@...>, <netdev@...>
Date: Thursday, April 24, 2008 - 12:13 pm

* Pavel Emelyanov (xemul@openvz.org) wrote:

True. This is by no mean an exhaustive list of network events. It just
happens to be the ones which has been useful to LTT/LTTng users for the
past ~10 years.


I doubt the current notification hooks have a performance impact as
small as the proposed markers. Which notification mechanism do you refer
to ? It could be interesting to put markers in there instead.

The goal behind this is to feed information to a general purpose tracer
like lttng, a scripting mechanism like systemtap or a special-purpose
tracer like ftrace.

I think that the most important instrumentation in this patchset is the
xmit/recv of a packet at the device level. The net_socket_*
instrumentation could eventually be replaced by an architecture specfic
system call parameters instrumentation.

Mathieu


-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[patch 37/37] LTTng instrumentation net, Mathieu Desnoyers, (Thu Apr 24, 11:04 am)
Re: [patch 37/37] LTTng instrumentation net, Pavel Emelyanov, (Thu Apr 24, 11:52 am)
Re: [patch 37/37] LTTng instrumentation net, Mathieu Desnoyers, (Thu Apr 24, 12:13 pm)
Re: [patch 37/37] LTTng instrumentation net, Pavel Emelyanov, (Thu Apr 24, 12:30 pm)
speck-geostationary