@AndresFreundTec We have read/recv support for the selectable buffers, but not readv/recvmsg. Pondering how best to do that, as we can only pass back on buffer ID per request. This breaks with multiple vecs. We could copy back the iov with updated ->iov_base? Ignoring const...
What would it precisely mean to do a readv with automatic buffer selection? Use multiple buffers, one for each iov, even if they're larger than necessary? I'm not sure I see the use case? Which const would have to be ignored if the iov would be updated? You mean readv()'s?
-
-
Assuming the app isn't being dumb, the buffers should fit. But it probably makes sense to just say "vectored IO is fine, but one vector only". For const, I mean readv etc generally take a const pointer. But if we copy back the ->iov_base updates, it's not. But moot if we go 1.
-
Actually even 1 is problematic, as the user iovec import verifies addresses... So it'd still need to copy in/out, unless I do some refactoring of the core bits.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.