I would have expected SO_RCVBUF to adjust the application-visible buffer
size for a UDP socket, the TCP window size for a TCP socket, and the raw
buffer size for a raw socket.
The reason I expect this is that an application dealing with a UDP
socket shouldn't have to know the UDP, IP and MAC header sizes. What if
you pass it a non-ethernet bound address, and IPV6 bound socket, some
other datagram type, an IP with source route, etc.?
So perhaps the SO_RCVBUF sockopt should be changed to reflect this?
Or another sockopt, SO_APPRCVBUF?
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/