Messages in this thread | | | From | "David Schwartz" <> | Subject | RE: UDP recvmsg blocks after select(), 2.6 bug? | Date | Sat, 16 Oct 2004 17:30:23 -0700 |
| |
> I don't think he is, but if he is: > > I'm not sure that either is reasonable behaviour. The socket buffers > don't increase or decrease at run time, do they? If they do shrink at > run time, this is news to me...
The socket buffers are not guaranteed to indicate a particular number of bytes in a sense that it meaningful to the application. In fact, on Linux, they don't mean application bytes.
In any event, we aren't talking about any particular implementation, we are talking about a standard. So what Linux does or doesn't do in response to memory pressure isn't relevant. What's relevant is what the standard actually guarantees and what the semantics of the protocols themselves are.
UDP is not reliable. Packets can be dropped, mangled, and lost. Nothing in POSIX prohibits an implementation from dropping a packet right before you call 'recvmsg'.
DS
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |