summaryrefslogtreecommitdiff
path: root/include/net/sctp/constants.h
diff options
context:
space:
mode:
authorYafang Shao <laoar.shao@gmail.com>2018-04-20 18:18:26 +0300
committerDavid S. Miller <davem@davemloft.net>2018-04-23 16:58:18 +0300
commit6163849d289be6ff2acd2fb520da303dec3219f0 (patch)
treeeae33c4b1790e66fc82abc0fca1d16254621e4b8 /include/net/sctp/constants.h
parent48d7a07ba355c7056e66adcdd35379d12e48252b (diff)
downloadlinux-6163849d289be6ff2acd2fb520da303dec3219f0.tar.xz
net: introduce a new tracepoint for tcp_rcv_space_adjust
tcp_rcv_space_adjust is called every time data is copied to user space, introducing a tcp tracepoint for which could show us when the packet is copied to user. When a tcp packet arrives, tcp_rcv_established() will be called and with the existed tracepoint tcp_probe we could get the time when this packet arrives. Then this packet will be copied to user, and tcp_rcv_space_adjust will be called and with this new introduced tracepoint we could get the time when this packet is copied to user. With these two tracepoints, we could figure out whether the user program processes this packet immediately or there's latency. Hence in the printk message, sk_cookie is printed as a key to relate tcp_rcv_space_adjust with tcp_probe. Maybe we could export sockfd in this new tracepoint as well, then we could relate this new tracepoint with epoll/read/recv* tracepoints, and finally that could show us the whole lifespan of this packet. But we could also implement that with pid as these functions are executed in process context. Signed-off-by: Yafang Shao <laoar.shao@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/net/sctp/constants.h')
0 files changed, 0 insertions, 0 deletions