PATCH: Integrating libev with other runloops

[Ryan Dahl]

On Sun, Oct 24, 2010 at 6:56 AM, Marc Lehmann <schmorp at schmorp.de> wrote:
> On Sun, Oct 24, 2010 at 02:48:29PM +0200, Rasmus Andersson <rasmus at notion.se> wrote:
>> 3. Can I live without helping libev poll when the kernel has one or
>> more reads pending (i.e. not registering for events on the backend
>> FD)?
>
> Not sure what you mean, but not all backends have an fd, and not all
> who do work in the way you would need it. Libev tells you that it is
> ready to poll (and the kernel state is updated) when it calls the release
> callback - no need to expose an internal number that might or might not be
> relevant, depending on the backend.

What if the new feature provided a special pipe for backends which do
not have an FD or do not have an FD which could be polled upon?
(Obviously it would be necessary for this pipe to not exist when the
feature was turned off.)