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

Visibility into early Rx / late Tx #292

Open
atenart opened this issue Nov 28, 2023 · 0 comments
Open

Visibility into early Rx / late Tx #292

atenart opened this issue Nov 28, 2023 · 0 comments

Comments

@atenart
Copy link
Contributor

atenart commented Nov 28, 2023

A few ideas here (we can split this as needed later):

  • Use the NIC timestamping feature to timestamp packets in the NIC itself, so we can later compare it to the timestamp of events and report any unexpected delay. This is not that trivial because not all NIC support it, clocks need to be synced and the whole thing would modify the system config/behavior so that might not be used in all cases.
  • Add a generic XDP program to report events early/late. The difficulty here is how to correlate the packet with the skb tracking logic. Part of the answer could be to hash the packet like what our OvS module is doing.
  • Add a post-processing command dedicated to latency, or improve the existing ones. Also this might fit even better in a generic Python post-processing command, see Post-processing in a Python interpreter  #35.
  • Improve the BPF side performances and allow to restrict what happens so we introduce as little extra latency as possible. Some options: Move the hook filtering choice to Rust #219 and Move common section handling after hooks ran #188.
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