t;>> 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
>&g
hought/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 lik
> 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.
>
> See the netgpu patches th
.
>
> i envision something like a new flag like MSG_ZEROCOPY_FIXED that
> "does the right thing" in the send vs recv paths.
See the netgpu patches that I posted earlier; these will handle
protocol independent zerocopy sends/receives. I do have a working
UDP receive implementation which will be posted with an updated
patchset.
--
Jonathan
fore. 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
