mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valentin Nechayev <netch@netch.kiev.ua>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch, rfc] lt-epoll ( level triggered epoll ) ...
Date: Fri, 14 Mar 2003 17:59:48 +0200	[thread overview]
Message-ID: <20030314155947.GD13106@netch.kiev.ua> (raw)
In-Reply-To: <20030311142447.GA14931@bjl1.jlokier.co.uk.lucky.linux.kernel>

 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.

Linus was true: Linux is just for fun, not for work.

I say nothing bad for the real work to implement it. But the person who said
"Do poor, do incompatible, but do our own" should be blamed. You know him.


-netch-

  parent reply	other threads:[~2003-03-14 15:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 20:15 Davide Libenzi
2003-03-11  4:32 ` Niels Provos
2003-03-11 18:15   ` Davide Libenzi
2003-03-11 20:04     ` Niels Provos
2003-03-12 18:05   ` Martin Waitz
2003-03-12 18:36     ` Davide Libenzi
2003-03-11  9:34 ` bert hubert
2003-03-11 18:20   ` Davide Libenzi
2003-03-12 12:05     ` bert hubert
2003-03-12 17:17       ` Davide Libenzi
2003-03-11 14:24 ` Jamie Lokier
2003-03-11 18:27   ` Davide Libenzi
2003-03-11 16:10 ` Giuliano Pochini
2003-03-11 18:34   ` Davide Libenzi
2003-03-12 18:08   ` Martin Waitz
2003-03-12 18:30     ` Davide Libenzi
2003-03-12 19:21       ` Martin Waitz
2003-03-12 19:39         ` Davide Libenzi
2003-03-12 19:57           ` Martin Waitz
     [not found] ` <20030311142447.GA14931@bjl1.jlokier.co.uk.lucky.linux.kernel>
2003-03-14 15:59   ` Valentin Nechayev [this message]
2003-03-14 16:53     ` Davide Libenzi
2003-03-14 17:56       ` Tim Smith
2003-03-14 19:01         ` Davide Libenzi
     [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     ` [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> Jonathan Lemon
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=20030314155947.GD13106@netch.kiev.ua \
    --to=netch@netch.kiev.ua \
    --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®