From: Eric Varsanyi <e0216@foo21.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: epoll vs stdin/stdout
Date: Tue, 8 Jul 2003 11:02:06 -0500 [thread overview]
Message-ID: <20030708160206.GP9328@srv.foo21.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0307080840400.4544@bigblue.dev.mcafeelabs.com>
On Tue, Jul 08, 2003 at 08:42:29AM -0700, Davide Libenzi wrote:
> It is not that events are delivered per-fd. If 3 and 4 refer to the same
> file* and you register both 3 and 4 with EPOLLIN, you'll get two events if
> an EPOLLIN happen. One for 3 and one for 4.
Agreed 100%, this is roughly what would happen with select() as well which
IMO is good (not surprising behaviour) for event loop writers: it would
return with both bits set. The EEXIST we were getting before this patch
would be analogous to select() returning an error if you set 2 bits that
where for fd's sharing an object (even across read/write bit vectors).
One could argue at the logic of having 2 fd's get read events on a
shared underlying object, but one read and the other write certainly
makes sense as discussed earlier.
Thanks again,
-Eric Varsanyi
next prev parent reply other threads:[~2003-07-08 15:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 15:48 epoll vs stdin/stdout Eric Varsanyi
2003-07-07 18:57 ` Davide Libenzi
2003-07-07 19:47 ` Eric Varsanyi
2003-07-07 20:03 ` Jamie Lokier
2003-07-07 20:18 ` Miquel van Smoorenburg
2003-07-07 21:20 ` H. Peter Anvin
2003-07-07 22:11 ` Davide Libenzi
2003-07-08 0:24 ` Jamie Lokier
2003-07-08 0:23 ` Davide Libenzi
2003-07-07 22:12 ` Davide Libenzi
2003-07-07 23:26 ` Davide Libenzi
2003-07-08 0:32 ` Jamie Lokier
2003-07-08 0:32 ` Davide Libenzi
2003-07-08 0:52 ` Jamie Lokier
2003-07-08 1:13 ` Davide Libenzi
2003-07-08 12:34 ` Jamie Lokier
2003-07-08 13:51 ` Jamie Lokier
2003-07-08 15:20 ` Davide Libenzi
2003-07-08 15:46 ` Eric Varsanyi
2003-07-08 15:42 ` Davide Libenzi
2003-07-08 16:02 ` Eric Varsanyi [this message]
2003-07-08 17:06 ` Davide Libenzi
2003-07-08 18:40 ` Eric Varsanyi
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=20030708160206.GP9328@srv.foo21.com \
--to=e0216@foo21.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;
as well as URLs for NNTP newsgroup(s).