Replies: 1 comment 2 replies
-
|
@mind-fuzzy The current tcppktlat can only track incoming packet latency between tcp receiving packet and the packet assigned to a user space. it does not support tracking latency for outgoing packets. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
As per the documentation of tcppktlat tool, it seems to trace the latency between TCP received pkt and picked up by userspace thread.
And looking at the implementation it seems to use the raw tracepoint
tcp_probeandtcp_rcv_space_adjustto track the incoming and outgoing time to then calculate the latency.tcp_probetracepoint is attcp_rcv_establishedwhich to my understanding is when the packet is received when the connection is in an established state. Which makes sense to me to track the incoming time.However, I don't quite get how using
tcp_rcv_space_adjustwould provide us the outgoing time.. Isn't it traced when the receive buffer needs to be adjusted, which isn't always. So wouldn't it be better iftcp_recvmsgis used ?Beta Was this translation helpful? Give feedback.
All reactions