Re: epoll behaviour after running out of descriptors

[Davide Libenzi]

On Sun, 2 Nov 2008, Olaf van der Spek wrote:

> On Sun, Nov 2, 2008 at 8:17 PM, Davide Libenzi <davidel@xxxxxxxxxxxxxxx> wrote:
> > On Sun, 2 Nov 2008, Olaf van der Spek wrote:
> >
> >> On Sun, Nov 2, 2008 at 7:48 PM, Davide Libenzi <davidel@xxxxxxxxxxxxxxx> wrote:
> >> > Why don't you grep for TIME_WAIT?
> >>
> >> Because I don't have access to the test environment at the moment.
> >
> > Here:
> >
> > http://tinyurl.com/5ay86v
> 
> I know what TIME_WAIT is. I just think it's not applicable to this situation.

It is. You are saturating the port space, so no new POLLIN/accept events 
are sent (until some TIME_WAIT clears), so epoll_wait() returns nothing 
(or does not return, if INF timeo).
Keeping only 1K (if this is what you meant with your *only* 1K) 
connections *alive*, does not mean the trail that does moving 1K 
connections leave, is free.
If you ever played with things like httperf, you should know what I'm 
talking about.



- Davide


--
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/