[lkml]   [2004]   [Oct]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRE: UDP recvmsg blocks after select(), 2.6 bug?

    > David Schwartz wrote:

    > > Perhaps I missed the details, but under your proposal, how
    > > do you predict
    > > at 'select' time what mode the socket will be in at 'recvmsg' time?!

    > Well, if you've got a blocking socket, and do a nonblocking read with
    > MSG_DONTWAIT, everything works fine. You lose a bit of
    > performance, but it works.
    > The problem case is if you create a socket, set O_NONBLOCK, do
    > select, clear
    > O_NONBLOCK, then do a recvmsg().
    > I suspect it's not a very common thing to do, so my proposal
    > would still help
    > the vast majority of existing apps.
    > Chris

    I think this is a reasonable thing to do. Applications that select in one
    mode and then operate in another are rare, and the suggested change won't
    break anything.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:07    [W:0.020 / U:63.628 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site