James Carlson wrote:
I can imagine at least three different intended semantics for this
ioctl when used with TCP:
1. It reports all unsent data.
2. It reports all unsent and unacknowledged data.
3. It reports all unsent and unacknowledged data, plus unread data
at the peer's side.
The _only_ usage model I've ever seen for this ioctl is (3) -- but if
you have another, I'd certainly like to know about it, and I'd update
the CR with that information.
I'd like (2). I have a problem with network equipment - peer always read
data it received, but sometimes router breaks the connection.
I'd like to resend unacknowledged data on next connection.
Another use is to implement lingering in userspace. In single-threaded
server it is not desirable to hang on socket close.
Regards,
Wojtek
_______________________________________________
networking-discuss mailing list
[email protected]
