On Monday 31 July 2006 17:00, David Miller wrote:
>
> So we'd have cases like this, assume we start with a full event
> queue:
>
> thread A thread B
>
> dequeue event
> aha, new connection
> accept()
> register new kevent
> queue is now full again
> add kevent on new
> connection
>
> At this point thread A doesn't have very many options when the kevent
> add fails. You cannot force this thread to read more events, since he
> may not be in a state where he is easily able to do so.
There has to be some thread that is responsible for reading events. Perhaps a
reasonable thing for a blocked thread that cannot process events to do is to
yield to one that can?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
