From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Li Yu <raise.sail@gmail.com>,
linux-kernel@vger.kernel.org, davidel@xmailserver.org
Subject: Re: The thundering herd like problem when multi epolls on one fd
Date: Sat, 14 Jan 2012 16:57:13 +0100 [thread overview]
Message-ID: <20120114155713.GA2966@hell> (raw)
In-Reply-To: <1326547247.5287.19.camel@edumazet-laptop>
* Eric Dumazet | 2012-01-14 14:20:47 [+0100]:
>What happens if the awaken thread does not consume the event, and prefer
>to exit ?
>
>If several threads are doing select()/poll()/epoll() on a shared fd,
>they _all_ must be notified the fd is ready, as manpages claim.
>
And if it is intended? Signaled via a new epoll_ctl() epoll_event flag? E.g.
EPOLLEXCLUSIVE
>Doing otherwise would require the prior consent of the user, using a
>special flag for example, and documentation.
Oops, yes. A fanout like mechanism _may be_ superior, but I think tests will
show some improvements anyway.
Hagen
next prev parent reply other threads:[~2012-01-14 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 11:13 The thundering herd like problem when multi epolls on one fd Li Yu
2012-01-14 13:20 ` Eric Dumazet
2012-01-14 15:57 ` Hagen Paul Pfeifer [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-15 15:41 Li Yu
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=20120114155713.GA2966@hell \
--to=hagen@jauu.net \
--cc=davidel@xmailserver.org \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raise.sail@gmail.com \
/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