From: Jamie Lokier <jamie@shareable.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Eric Varsanyi <e0216@foo21.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: epoll vs stdin/stdout
Date: Tue, 8 Jul 2003 01:24:44 +0100 [thread overview]
Message-ID: <20030708002444.GA12127@mail.jlokier.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.55.0307071506560.4704@bigblue.dev.mcafeelabs.com>
Davide Libenzi wrote:
> It has to keep (file*, fd) as hashing key. That will work out just fine.
Do you mean epoll has to use (file*,fd) as the hash key?
> Not even thinking changing the API since it'll break existing apps.
Oh, you're right. I forgot that apps wait for both read & write on
the same network fd... duh! :)
> The above trick will do it. Going to test it ...
Good-oh.
-- Jamie
next prev parent reply other threads:[~2003-07-08 0:10 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 [this message]
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
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=20030708002444.GA12127@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=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).