From: Dan Kegel <dank@kegel.com>
To: Jonathan Lemon <jlemon@flugsvamp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /dev/epoll update ...
Date: Tue, 25 Sep 2001 11:34:25 -0700 [thread overview]
Message-ID: <3BB0CE31.2446D3F9@kegel.com> (raw)
In-Reply-To: <local.mail.linux-kernel/3BAEB39B.DE7932CF@kegel.com> <local.mail.linux-kernel/3BAF83EF.C8018E45@distributopia.com> <200109251736.f8PHamf40636@prism.flugsvamp.com>
Jonathan Lemon wrote:
>
> In article <local.mail.linux-kernel/3BB03C6A.7D1DD7B3@kegel.com> you write:
> >Right, and kqueue() can't even represent the 'level triggered' style --
> >or at least it isn't clear from the paper that it can!
>
> Yes it does - kqueue() is 'level-triggered' by default.
Apologies for the line noise. I've corrected
http://www.kegel.com/c10k.html to show kqueue as both edge- and level- triggered.
Further corrections welcome...
> As Christopher pointed out, any event can be converted into an
> edge-triggered style notification simply by setting EV_CLEAR. However,
> this is not usually a popular model from a programmer's point of view,
> as it increases the complexity of their app. (This is what I've seen, YMMV)
Agreed; the poll()-like semantics of level-triggering are particularly
forgiving.
- Dan
next prev parent reply other threads:[~2001-09-25 18:33 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <local.mail.linux-kernel/3BB03C6A.7D1DD7B3@kegel.com>
[not found] ` <local.mail.linux-kernel/3BAEB39B.DE7932CF@kegel.com>
[not found] ` <local.mail.linux-kernel/3BAF83EF.C8018E45@distributopia.com>
2001-09-25 17:36 ` [PATCH] /dev/epoll update Jonathan Lemon
2001-09-25 18:34 ` Dan Kegel [this message]
2002-03-20 3:49 [patch] " Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 4:16 [PATCH] " Dan Kegel
2001-09-24 19:11 ` Eric W. Biederman
2001-09-24 19:34 ` Jamie Lokier
2001-09-24 20:09 ` Davide Libenzi
2001-09-24 21:56 ` Jamie Lokier
2001-09-24 22:08 ` Davide Libenzi
2001-09-24 22:09 ` Jamie Lokier
2001-09-24 22:20 ` Davide Libenzi
2001-09-24 22:21 ` Jamie Lokier
2001-09-24 22:30 ` Davide Libenzi
2001-09-25 9:25 ` Dan Kegel
[not found] ` <3BAF83EF.C8018E45@distributopia.com>
2001-09-25 8:12 ` Dan Kegel
2001-09-21 6:22 Dan Kegel
2001-09-21 18:45 ` Davide Libenzi
2001-09-19 2:20 Dan Kegel
2001-09-19 6:25 ` Dan Kegel
2001-09-19 7:04 ` Christopher K. St. John
2001-09-19 15:37 ` Dan Kegel
2001-09-19 15:59 ` Zach Brown
2001-09-19 17:12 ` Christopher K. St. John
2001-09-19 17:39 ` Davide Libenzi
2001-09-19 18:26 ` Alan Cox
2001-09-19 17:25 ` Davide Libenzi
2001-09-19 19:03 ` Christopher K. St. John
2001-09-19 19:30 ` Davide Libenzi
2001-09-19 21:49 ` Christopher K. St. John
2001-09-19 22:11 ` Davide Libenzi
2001-09-19 23:24 ` Christopher K. St. John
2001-09-19 23:52 ` Davide Libenzi
2001-09-20 2:13 ` Dan Kegel
2001-09-20 2:28 ` Davide Libenzi
2001-09-20 3:03 ` Dan Kegel
2001-09-20 16:58 ` Davide Libenzi
2001-09-20 4:32 ` Christopher K. St. John
2001-09-20 4:43 ` Christopher K. St. John
2001-09-20 5:05 ` Benjamin LaHaise
2001-09-20 18:25 ` Davide Libenzi
2001-09-20 19:33 ` Benjamin LaHaise
2001-09-20 19:58 ` Davide Libenzi
2001-09-20 17:18 ` Davide Libenzi
2001-09-24 0:11 ` Gordon Oliver
2001-09-24 0:33 ` Davide Libenzi
2001-09-24 19:23 ` Eric W. Biederman
2001-09-24 20:04 ` Davide Libenzi
2001-09-21 5:59 ` Ton Hospel
2001-09-21 16:48 ` Davide Libenzi
2001-09-19 17:21 ` Davide Libenzi
2001-09-07 19:27 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=3BB0CE31.2446D3F9@kegel.com \
--to=dank@kegel.com \
--cc=jlemon@flugsvamp.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 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.