-
Notifications
You must be signed in to change notification settings - Fork 13
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
Support of Intel i225 TAPRIO Offload Feature #21
Comments
Not exactly so. The application just passes the buffer to the kernel using the
This program does not do forwarding. However, this is not to say that it is only for simple point-to-point topologies. It just is intended to be run on endpoints. In the situations I have needed isochron over multiple hops, the forwarding was handled by the Linux bridge, either in the kernel software path or directly offloaded to hardware (through switchdev and such). So there was no need for the packet to be passed to user space (isochron) and user space to decide where and when to forward it. If you could explain your use case in more detail, maybe I could reconsider this. |
Thank you for getting back to me so quickly. Sure, our use-case is that we have multiple hops with OvS on each hop and would like to run Thank you for looking into it and if you think the |
Hello,
We are considering using
isochron
for our evaluations and I am wondering if it also supports the TAPRIO in HW offload (flags 0x2
https://man7.org/linux/man-pages/man8/tc-taprio.8.html) for these scenarios:isochron
in simple Point-to-Point topologyisochron
for more than P2P where the next hop is also a Linux machine equipped with Intel i225.Option 1. should be pretty straightforward based on the docs, but I am unsure about the second option. If I understand the
flags 0x2
, the application has to specifytxtime
itself and then pass it to the NIC. That would mean thatisochron
would need to receive the packet and also handle its forwarding on each additional hop. Am I correct?Thanks for your time and clarifications!
The text was updated successfully, but these errors were encountered: