Re: UDP recvmsg blocks after select(), 2.6 bug?

[Chris Friesen]

Richard B. Johnson wrote:
> On Wed, 6 Oct 2004, David S. Miller wrote:

> > There is no such guarentee.
> Huh?  Then why would anybody use select()?  

To tell you when to try a nonblocking read?

> It can't return a
> 'guess" or it's broken. When select() or poll() claims that
> there are data available, there damn well better be data available
> or software becomes a crap-game.

In the single-threaded case, where you are the only one touching the socket, I 
would expect this to be true.  But since I'm a belt-and-suspenders kind of guy, 
I usually use nonblocking reads anyway.

Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/