I also saw what I believe is a problem with select, but I haven't had
time to poke around the kernel to try to understand it. In my case,
the problem is that when I have raw sockets reading ethernet frames,
select will not return immediately when there is a packet ready. When
it does return, due to timeout, or another FD in the set being ready
for action, the FD is set correctly though. My hack/kludge/work-around
was to sleep for a max of 5ms, but that is not a clean, or efficient
solution. Another person sent private email to me claiming that he
saw the same problem, so it's likely I'm not insane on this issue :)
So, I do think there may be problems with select, but I'm not sure if it
relates to your problem or not.
Ben
>
> I'm not subsribed on the list, so when replying this you may consider
> Cc:ing me.
>
> --
> M. Tavasti / tawz@nic.fi / +358-40-5078254
> -
> 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/
-- Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com> President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear - 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/