-
Notifications
You must be signed in to change notification settings - Fork 568
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
SHARED_UMEM creation #427
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi all,
currently I am writing a pure golang library for using AF_XDP sockets. Little heads up: I do not want or need any support in my go code :)
I rather have a question regarding the creation of multiple sockets sharing UMEM. I have been reading the source-code of the tutorials here as well as the source of libxdp and I am none the wiser.
If I understand correctly, to create multiple XSKs with a single shared UMEM you would go along the lines of this:
For the first socket:
For all further sockets:
flags |= XDP_SHARED_UMEM
and set the shared_umem_fd to the fd of the first socket.If I do that, the bind-syscall returns "EINVAL" and after countless hours of debugging I am out of options of what values are considered invalid. Right now I am questioning if I am understanding this procedure correctly of if I am missing something.
Maybe someone here can help me.
Much appreciated!
The text was updated successfully, but these errors were encountered: