lkml.org 
[lkml]   [2001]   [Sep]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] /dev/epoll update ...
In article <local.mail.linux-kernel/3BB03C6A.7D1DD7B3@kegel.com> you write:
>"Christopher K. St. John" wrote:
>> Ok, just to confirm. Using the language of BSD's
>> kqueue[1]. you've got:
>>
>> a) report the event only once when it occurs aka
>> "edge triggered" (EV_CLEAR, not EV_ONESHOT)
>>
>> b) continuously report the event as long as the
>> state is valid, aka "level triggered"
>
>Right, and kqueue() can't even represent the 'level triggered' style --
>or at least it isn't clear from the paper that it can! True "level triggered"
>would require that the kernel track readiness of the affected file descriptors.

Yes it does - kqueue() is 'level-triggered' by default. You may want
to check my latest USENIX paper, which explains this, as well as some
performance measurements, at:

http://www.flugsvamp.com/~jlemon/fbsd/kqueue_usenix2001.pdf

The kernel validates the state (or "level") before returning the event
to the user, so the event is guaranteed to be valid at the time the
syscall returns.

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)
--
Jonathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:03    [W:0.046 / U:32.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site