Searched hist:"3847 ce32aea9fdf56022de132000e8cf139042eb" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/include/trace/events/ |
H A D | sock.h | 3847ce32aea9fdf56022de132000e8cf139042eb Fri Jun 17 07:00:03 CDT 2011 Satoru Moriya <satoru.moriya@hds.com> core: add tracepoints for queueing skb to rcvbuf
This patch adds 2 tracepoints to get a status of a socket receive queue and related parameter.
One tracepoint is added to sock_queue_rcv_skb. It records rcvbuf size and its usage. The other tracepoint is added to __sk_mem_schedule and it records limitations of memory for sockets and current usage.
By using these tracepoints we're able to know detailed reason why kernel drop the packet.
Signed-off-by: Satoru Moriya <satoru.moriya@hds.com> Acked-by: Neil Horman <nhorman@tuxdriver.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
/openbmc/linux/net/core/ |
H A D | net-traces.c | diff 3847ce32aea9fdf56022de132000e8cf139042eb Fri Jun 17 07:00:03 CDT 2011 Satoru Moriya <satoru.moriya@hds.com> core: add tracepoints for queueing skb to rcvbuf
This patch adds 2 tracepoints to get a status of a socket receive queue and related parameter.
One tracepoint is added to sock_queue_rcv_skb. It records rcvbuf size and its usage. The other tracepoint is added to __sk_mem_schedule and it records limitations of memory for sockets and current usage.
By using these tracepoints we're able to know detailed reason why kernel drop the packet.
Signed-off-by: Satoru Moriya <satoru.moriya@hds.com> Acked-by: Neil Horman <nhorman@tuxdriver.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|
H A D | sock.c | diff 3847ce32aea9fdf56022de132000e8cf139042eb Fri Jun 17 07:00:03 CDT 2011 Satoru Moriya <satoru.moriya@hds.com> core: add tracepoints for queueing skb to rcvbuf
This patch adds 2 tracepoints to get a status of a socket receive queue and related parameter.
One tracepoint is added to sock_queue_rcv_skb. It records rcvbuf size and its usage. The other tracepoint is added to __sk_mem_schedule and it records limitations of memory for sockets and current usage.
By using these tracepoints we're able to know detailed reason why kernel drop the packet.
Signed-off-by: Satoru Moriya <satoru.moriya@hds.com> Acked-by: Neil Horman <nhorman@tuxdriver.com> Signed-off-by: David S. Miller <davem@davemloft.net>
|