-
Notifications
You must be signed in to change notification settings - Fork 564
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
Xdp in run to completion and poll mode #373
Comments
With that sparse information you provided anything could be wrong. You have to submit enough information for someone else to reproduce your problem, otherwise we cannot help you. |
I understand that. |
Again, unfortunately depends on what you are doing :-). An Rx only workload can run without any syscalls. If you have a Tx only workload, then you need syscalls. If you have both, then you can generally run without any syscalls. But if you are using the need_wakeup feature, then processing might stop and you need to wakeup the driver with a syscall such as poll(), recvmsg(), or sendto(). Without need_wakeup on, the driver will busy-loop at 100% requiring no syscalls in zero-copy mode. |
I am having an observation where in some of the system with optical fiber adapter (sfp/sfp+) the run to completion mode is not working, only the poll mode is working.
In run to completion I am unable to see any packet received in the user space.
Is this expected ?
Can we have a solution for this?
Or any network setting I have to change
@magnus-karlsson @tohojo @dmitris @donaldh @netoptimizer
The text was updated successfully, but these errors were encountered: