From: Davide Libenzi <davidel@xmailserver.org>
To: Eric Varsanyi <e0216@foo21.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: epoll vs stdin/stdout
Date: Tue, 8 Jul 2003 08:42:29 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.55.0307080840400.4544@bigblue.dev.mcafeelabs.com> (raw)
In-Reply-To: <20030708154636.GM9328@srv.foo21.com>
On Tue, 8 Jul 2003, Eric Varsanyi wrote:
> On Mon, Jul 07, 2003 at 04:26:21PM -0700, Davide Libenzi wrote:
> > On Mon, 7 Jul 2003, Davide Libenzi wrote:
> > Try out this one, either over 2.5.74 or over an existing epoll-patched
> > 2.4.{20,21} ...
>
> This appears to be working as advertised, thanks!
>
> IMO it doesn't seem that evil to deliver events per-fd rather than
> per-file, this is similar to the semantic you get from select() on
> fd's sharing an object. To be surprised someone would have to have
> coded to the (previous) sharing visible nature of epoll and be expecting
> the EEXIST back when sharing was in play.
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.
- Davide
next prev parent reply other threads:[~2003-07-08 15:35 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 [this message]
2003-07-08 16:02 ` Eric Varsanyi
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=Pine.LNX.4.55.0307080840400.4544@bigblue.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=e0216@foo21.com \
--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).