From: Jonathan Lemon <jlemon@flugsvamp.com>
To: davidel@xmailserver.org, linux-kernel@vger.kernel.org
Subject: Re: [patch, rfc] lt-epoll ( level triggered epoll ) ... X-Newsgroups: local.mail.linux-kernel In-Reply-To: <local.mail.linux-kernel/Pine.LNX.4.50.0303140845480.1903-100000@blue1.dev.mcafeelabs.com>
Date: Fri, 14 Mar 2003 15:43:40 -0600 (CST) [thread overview]
Message-ID: <200303142143.h2ELheqx076668@mail.flugsvamp.com> (raw)
In-Reply-To: <local.mail.linux-kernel/20030314155947.GD13106@netch.kiev.ua>
In article <local.mail.linux-kernel/Pine.LNX.4.50.0303140845480.1903-100000@blue1.dev.mcafeelabs.com> you write:
>On Fri, 14 Mar 2003, Valentin Nechayev wrote:
>
>> Tue, Mar 11, 2003 at 14:27:50, jamie wrote about "Re: [patch, rfc]
>lt-epoll ( level triggered epoll ) ...":
>>
>> > Actually I think _this_ is cleanest: A three-way flag per registered
>> > fd interest saying whether to:
>> >
>> > 1. Report 0->1 edges for this interest. (Initial 1 counts as an event).
>> > 2. Continually report 1 levels for this interest.
>> > 3. One-shot, report the first time 1 is noted and unregister.
>> >
>> > ET poll is equivalent to 1. LT poll is equivalent to 2. dnotify's
>> > one-shot mode is equivalent to 3.
>>
>> kqueue can do all three variants (1st with EV_CLEAR, 3rd with EV_ONESHOT).
>>
>> So, result of this whole epoll work is trivially predictable - Linux will have
>> analog of "overbloated" and "poorly designed" kqueue, but more poor
>> and with incompatible interface, adding its own stone to hell of
>> different APIs. Congratulations.
>
>See, this is a free world, and I very much respect your opinion. On the
>other side you might want to actually *read* the kqueue man page and find
>out of its 24590 flags, where 99% of its users will use only 1% of its
>functionality. Talking about overbloating. You might also want to know
>that quite a few kqueue users currently running on your favourite OS, are
>moving to Linux+epoll. The reason is still unclear to me, but I can leave
>you to discover it as exercise.
FUD. You should know that in the normal case, kq users don't use any
flags, but they are available for those people who are doing specific
things. But I bet you knew that already and just want to slam something
that isn't epoll.
--
Jonathan
next parent reply other threads:[~2003-03-14 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <local.mail.linux-kernel/Pine.LNX.4.50.0303101139520.1922-100000@blue1.dev.mcafeelabs.com>
[not found] ` <local.mail.linux-kernel/20030311142447.GA14931@bjl1.jlokier.co.uk.lucky.linux.kernel>
[not found] ` <local.mail.linux-kernel/20030314155947.GD13106@netch.kiev.ua>
2003-03-14 21:43 ` Jonathan Lemon [this message]
2003-03-14 22:16 ` [patch, rfc] lt-epoll ( level triggered epoll ) Davide Libenzi
2003-03-14 22:27 ` Jonathan Lemon
2003-03-14 22:57 ` Davide Libenzi
2003-03-14 23:36 ` Jonathan Lemon
2003-03-15 0:06 ` 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=200303142143.h2ELheqx076668@mail.flugsvamp.com \
--to=jlemon@flugsvamp.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
all inboxes | Powered by JetHome®