From: "Olaf van der Spek" <olafvdspek@gmail.com>
To: "Davide Libenzi" <davidel@xmailserver.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: epoll behaviour after running out of descriptors
Date: Mon, 3 Nov 2008 09:07:40 +0100 [thread overview]
Message-ID: <b2cc26e40811030007w48c3e632v219b72fec1139b40@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0811021445260.9451@alien.or.mcafeemobile.com>
On Sun, Nov 2, 2008 at 11:49 PM, Davide Libenzi <davidel@xmailserver.org> wrote:
> At the time of the first EMFILE, you've filled up the fd space, but not
> the kernel listen backlog. Additions to the backlog, triggers new events,
Shouldn't ET only fire again *after* you drained the queue? When
accept returns EMFILE, you did not drain the queue.
> that you see after the first EMFILE. At a given point, the backlog is
> full, so no new half connections are dropped in there, so no new events
> are generated.
The backlog is 128 entries though, I don't see that many EMFILEs.
> Again, sleeping on (EMFILE && ET) is bad mojo,
It's not always best to free up descriptors right away.
> and nowhere is written that
> events should be generated in the EMFILE->no-EMFILE transitions.
That's true, but I'm saying that this might be handy to have.
prev parent reply other threads:[~2008-11-03 8:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 16:38 Olaf van der Spek
2008-11-02 18:25 ` Davide Libenzi
2008-11-02 18:33 ` Olaf van der Spek
2008-11-02 18:48 ` Davide Libenzi
2008-11-02 18:51 ` Olaf van der Spek
2008-11-02 19:10 ` Eric Dumazet
2008-11-02 19:15 ` Olaf van der Spek
2008-11-02 19:17 ` Davide Libenzi
2008-11-02 19:20 ` Olaf van der Spek
2008-11-02 19:27 ` Davide Libenzi
2008-11-02 20:41 ` Olaf van der Spek
2008-11-02 21:17 ` Davide Libenzi
2008-11-02 22:17 ` Olaf van der Spek
2008-11-02 22:49 ` Davide Libenzi
2008-11-03 8:07 ` Olaf van der Spek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2cc26e40811030007w48c3e632v219b72fec1139b40@mail.gmail.com \
--to=olafvdspek@gmail.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®