Skip to contentSkip to conversation

/dev/epoll update ...

PATCH Jonathan Lemon 1 participant 1 message Sep 25, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): local.mail.linux-kernel/[email protected]

#1 lore raw

In article <local.mail.linux-kernel/[email protected]> you write:

Quoted 7 lines
Quoted 6 lines · Christopher K. St. John

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)

Quoted 6 lines
Quoted 2 lines

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)

Signature · 1 line
Jonathan