-
Notifications
You must be signed in to change notification settings - Fork 235
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 for {recv,send}mmsg #493
Comments
The addition of {recv,send}mmsg would certainly be accepted. I'm afraid currently don't have a lot of time to work on this, but if you can send a pr from the changes you made I can take look at it. |
For sure! I just opened it: #494 |
Hi, I just want to say that this would be amazing to have in |
This has been implemented. |
Hi,
When working with DGRAM sockets, the
recvmmsg
andsendmmsg
syscalls are available to send multiple datagrams in a single syscall, potentially leading to increased performance (if the syscall rate is the bottleneck). I already have a draft available at https://github.com/Tuetuopay/socket2/tree/mmsg which is heavily inspired from the existingrecvmsg
/sendmsg
implementation, because I wanted to test it out.I'm opening the issue to discuss the API exposed, which is a bit simplified from the actual syscalls. The actual syscalls support scatter/gather buffers, just like
sendmsg
/recvmsg
, and are exposed bysocket2
; this however does not to keep the API in control. My questions are:_vectored
variants)MmsgHdr(Mut)
" is a valid option as it is done)_vectored
variants)I'm asking your opinion because the API is starting to look a lot like a full matrix of features with
recv(_multiple)?_from(_vectored)?
. Here is the added functions, with#[cfg]
removed for brievty:Thank you for your time!
The text was updated successfully, but these errors were encountered: