Re: [take24 0/6] kevent: Generic event handling mechanism.

[Ulrich Drepper <drepper@redhat.com>]

Evgeniy Polyakov wrote:
> > > Btw, what about putting aditional multiplexer into add/remove/modify
> > > switch? There will be logical 'ready' addon?
> > Is it needed?  Usually this is done with a *_wait call with a timeout of 
> > zero.  That code path might have to be optimized but it should already 
> > be there.
>
> It does not allow to mark events as ready.
> And current interfaces wake up when either timeout is zero (in this case
> thread itself does not sleep and can process events), or when there is
> _new_ work - since there is no _new_ work, when thread awakened to
> process it was killed, kernel does not think that something is wrong.

Rather than mark an existing entry as ready, how about a call to inject 
a new ready event?

This would be useful to implement functionality at userlevel and still 
use an event queue to announce the availability.  Without this type of 
functionality we'd need to use indirect notification via signal or pipe 
or something like that.

--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-
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/