hi all, i'm seeking input / comment on the idea of implementing full fledged zerocopy UDP networking that uses persistent buffers allocated in userspace... before I go off on a solo tangent with my first patches lol.
i'm sure there's been lots of thought/discussion on this before. of course Willem added MSG_ZEROCOPY on the send path (pin buffers on demand / per send). and something similar to what I speak of exists with TCP_ZEROCOPY_RECEIVE. i envision something like a new flag like MSG_ZEROCOPY_FIXED that "does the right thing" in the send vs recv paths. Victor