From: "Michael Kerrisk" <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Sam Varshavchik <mrsam-W1w4QoW4mIDgLSHwZvcCBg@public.gmane.org>,
Davide Libenzi <davidel-AhlLAIvw+VEjIGhXcJzhZg@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: epoll(7) redux
Date: Wed, 9 Apr 2008 13:15:15 +0200 [thread overview]
Message-ID: <cfd18e0f0804090415m1ddb36bahce8e6b724e60da7d@mail.gmail.com> (raw)
In-Reply-To: <cone.1207739243.602382.23947.500-lO+bjgoT4TKm14v+eVDVcBDJ/jce7dRH@public.gmane.org>
On Wed, Apr 9, 2008 at 1:07 PM, Sam Varshavchik <mrsam-W1w4QoW4mIDgLSHwZvcCBg@public.gmane.org> wrote:
> Q2
>
> Can two epoll sets wait for the same file descriptor? If so, are events
> reported to both epoll file descriptors?
>
> A2
>
> Yes, and events would be reported to both. However, it is not recommended.
>
> =========
>
> It's not clear what "not recommended" means. Furthermore, I don't think
> there's anything wrong with two epoll file descriptors waiting for different
> events on the same file descriptor. One's waiting for POLLIN, the other for
> POLLOUT. What's wrong with that?
Perhaps Davide has some thought to offer here?
--
Michael Kerrisk
Maintainer of the Linux man-pages project
http://www.kernel.org/doc/man-pages/
Want to report a man-pages bug? Look here:
http://www.kernel.org/doc/man-pages/reporting_bugs.html
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-04-09 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 11:07 epoll(7) redux Sam Varshavchik
[not found] ` <cone.1207739243.602382.23947.500-lO+bjgoT4TKm14v+eVDVcBDJ/jce7dRH@public.gmane.org>
2008-04-09 11:15 ` Michael Kerrisk [this message]
[not found] ` <cfd18e0f0804090415m1ddb36bahce8e6b724e60da7d-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-04-09 19:15 ` Davide Libenzi
2008-04-09 22:43 ` Sam Varshavchik
[not found] ` <cone.1207780987.222099.27997.500-lO+bjgoT4TKm14v+eVDVcBDJ/jce7dRH@public.gmane.org>
2008-05-21 17:53 ` Michael Kerrisk
[not found] ` <483461AE.9080305-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-05-21 19:01 ` Davide Libenzi
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=cfd18e0f0804090415m1ddb36bahce8e6b724e60da7d@mail.gmail.com \
--to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=davidel-AhlLAIvw+VEjIGhXcJzhZg@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mrsam-W1w4QoW4mIDgLSHwZvcCBg@public.gmane.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