From: William Lee Irwin III <wli@holomorphy.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Dan Kegel <dank@kegel.com>, John Myers <jgmyers@netscape.com>,
linux-aio@kvack.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Comparing the aio and epoll event frameworks.
Date: Mon, 19 May 2003 18:02:58 -0700 [thread overview]
Message-ID: <20030520010258.GQ2444@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0305191743230.6565@bigblue.dev.mcafeelabs.com>
Davide Libenzi wrote:
>>> Adding a single shot feature to epoll takes about 5 lines of code,
>>> comments included :) You know how many reuqests I had ? Zero, nada.
On Mon, 19 May 2003, Dan Kegel wrote:
>> I thought edge triggered epoll *was* single-shot.
On Mon, May 19, 2003 at 05:47:15PM -0700, Davide Libenzi wrote:
> For single shot I mean that once you receive one event, you will not
> receive more events for that fd if you do not rearm it. Suppose you
> receive 1000 bytes of data and you get an event (EPOLLIN). If after 10
> seconds you receive another 1000 bytes, you will receive another event.
> This is not single shot.
I think this would be useful for network daemons that would like to
fairly schedule responses (i.e. not re-arm until a client on a given fd
deserves a turn again). IRC daemons would appear to be a perfect
candidate for such. OTOH you may want to wait until someone is writing
such a beast so "it will be used" instead of "it is potentially useful".
-- wli
next prev parent reply other threads:[~2003-05-20 0:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 23:33 Comparing the aio and epoll event frameworks John Myers
2003-05-20 0:38 ` Davide Libenzi
2003-05-20 1:10 ` Dan Kegel
2003-05-20 0:46 ` William Lee Irwin III
2003-05-20 0:52 ` Davide Libenzi
2003-05-20 0:47 ` Davide Libenzi
2003-05-20 1:02 ` William Lee Irwin III [this message]
2003-05-20 1:37 ` Dan Kegel
2003-05-20 1:15 ` William Lee Irwin III
2003-05-20 2:06 ` Dan Kegel
2003-05-20 1:22 ` Dan Kegel
2003-05-20 0:58 ` 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=20030520010258.GQ2444@holomorphy.com \
--to=wli@holomorphy.com \
--cc=dank@kegel.com \
--cc=davidel@xmailserver.org \
--cc=jgmyers@netscape.com \
--cc=linux-aio@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.