Re: [Libevent-users] Asynchronous writes in the event loop model

[Nick Mathewson <nickm@xxxxxxxxxxxxx>]

On Mon, Feb 6, 2012 at 4:46 PM, Adrian Chadd <adrian@xxxxxxxxxxxxxxx> wrote:
> Hi,
>
> the standard trick:
>
> * designate one thread as "signals here" and block signals on all other threads;

Actually, if we're willing to require that the user block signals on
non-"signals here" threads themself, we can do a lot better than our
current silliness on a couple more platforms: using signalfd on Linux
would become a lot simpler.

Naturally, we couldn't do this by default, since .  But as an option
for the event_base_config, it might work nicely.

> * use pipes for sending signals between threads (ie, to wake them up);

That's what we do on non-kqueue platforms now.

> * wish that kqueue and similar methods were portable.

If every platform had kqueue, Niels would never have started Libevent
in the first place. ;)

yrs,
-- 
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.