Anders Persson wrote:
But does read() straddle b_next boundaries? (It didn't prior to
Volo, partly to handle urgent data correctly.) It clearly can't
straddle b_next boundaries for UDP.
No, read() does not. But the data_in_proc callback processes all the
available data, even if read() ends up copying a single datagram.
If we know that the all the consumers (read, recv*, ksock*) do not
straddle b_next boundaries, what is the benefit of adding the complexity
to pass b_next chains through data_in_proc?
Erik
_______________________________________________
networking-discuss mailing list
[email protected]
