Messages in this thread | | | From | "Hua Zhong" <> | Subject | RE: UDP recvmsg blocks after select(), 2.6 bug? | Date | Thu, 7 Oct 2004 11:20:32 -0700 |
| |
> This actually sounds quite interesting. > > For applications that are prepared to handle the nonblocking > case, you get full speed. For applications coded to POSIX, > you get correctness. > > It does mean that select() is now a bit more complicated, but > applications become much easier to write.
It was my original proposal. The only question is to return which error code. We cannot return EAGAIN as Posix explicitly disallows it. Is EIO good? Or some other new error code?
As far as implmentation goes, we probably need a "check_data" function in the f_ops. Default it could be NULL.
The question is that is it worth the trouble to be Posix complaint? Seems most developers think not, especially since it has been this way for so long a time.
Hua
- 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/
| |