Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate use of SO_TIMESTAMPING to get timestamps for sent packets #35

Open
brendonj opened this issue Aug 12, 2019 · 1 comment
Open

Comments

@brendonj
Copy link
Contributor

brendonj commented Aug 12, 2019

Investigate whether SO_TIMESTAMPING will work for AMP, and if so, what is required to implement it.

Is SO_TIMESTAMPING available in popular kernels? Do we need particular hardware to make it work? Will it work with a variety of socket types (raw, tcp, udp)?

Can we replace the current packet timestamping calls that use gettimeofday() with this and retrieve actual sending times from the socket? Should we replace the receive timestamp code using SO_TIMESTAMP with this also?

See: https://www.kernel.org/doc/Documentation/networking/timestamping.txt

brendonj pushed a commit that referenced this issue Nov 15, 2019
Get the software timestamp for when packets were actually sent rather than
relying on a call to gettimeofday() immediately before calling sendto().

See #35.
@brendonj
Copy link
Contributor Author

Looks like udpstream and tcpping use gettimefoday() and sendto() instead of delay_send_packet(), if possible they should use the same approach as the other similar tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant