aboutsummaryrefslogtreecommitdiffstats
path: root/include/net
diff options
context:
space:
mode:
authorGeneviève Bastien <gbastien@versatic.net>2018-11-27 12:52:39 -0500
committerDavid S. Miller <davem@davemloft.net>2018-11-30 13:23:25 -0800
commitb0e3f1bdf9e7140fd1151af575f468b5827a61e1 (patch)
tree7aba1b163e88451acfc69e0a168bb4d84cf4cea0 /include/net
parentnet/flow_dissector: correct comments on enum flow_dissector_key_id (diff)
downloadlinux-dev-b0e3f1bdf9e7140fd1151af575f468b5827a61e1.tar.xz
linux-dev-b0e3f1bdf9e7140fd1151af575f468b5827a61e1.zip
net: Add trace events for all receive exit points
Trace events are already present for the receive entry points, to indicate how the reception entered the stack. This patch adds the corresponding exit trace events that will bound the reception such that all events occurring between the entry and the exit can be considered as part of the reception context. This greatly helps for dependency and root cause analyses. Without this, it is not possible with tracepoint instrumentation to determine whether a sched_wakeup event following a netif_receive_skb event is the result of the packet reception or a simple coincidence after further processing by the thread. It is possible using other mechanisms like kretprobes, but considering the "entry" points are already present, it would be good to add the matching exit events. In addition to linking packets with wakeups, the entry/exit event pair can also be used to perform network stack latency analyses. Signed-off-by: Geneviève Bastien <gbastien@versatic.net> CC: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> CC: Steven Rostedt <rostedt@goodmis.org> CC: Ingo Molnar <mingo@redhat.com> CC: David S. Miller <davem@davemloft.net> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org> (tracing side) Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions