>> I must think a bit how to automate this. Please give me time.
>
> Maybe you could use the EVLOOP_NONBLOCK flag to event_loop(), and call
> it twice, and verify that in the edge-triggered case the event is only
> activated on the first call, but in the level-triggered case the event
> is activat
On Thu, May 29, 2008 at 08:02:18PM +0200, Valery Kholodkov wrote:
>
> For the convenience I'll answer to Nick's questions from
> SF's patch tracker in this list.
>
> > A few initial questions:
> > - How exactly does the test_et.c file test the edge-triggered behavior?
> > As near as I can tell,
For the convenience I'll answer to Nick's questions from
SF's patch tracker in this list.
> A few initial questions:
> - How exactly does the test_et.c file test the edge-triggered behavior?
> As near as I can tell, the test ought to pass whether EV_ET works or not.
> What am I missing?
I hardl
>> This patch introduces EV_ET flag. Whenever you specify EV_ET in
>> event_set
>> call a specific module will try enforce Edge-Triggered behaviour.
>
> Well, not exactly. The way the patch is written now, when EV_ET is
> set, *and* you're using the epoll backend or the kqueue backend,
> you'll g
On Thu, May 29, 2008 at 05:40:16PM +0200, Valery Kholodkov wrote:
> Greetings!
>
> Since discovering libevent for myself I've been wondering
> why where is still no support for Edge-Triggered behaviour, which
> from my point of view could be easily implemented.
Basically, because nobody had writt
Greetings!
Since discovering libevent for myself I've been wondering
why where is still no support for Edge-Triggered behaviour, which
from my point of view could be easily implemented.
There were many talks already among Linux kernel developers
as well as application developers about how and why
