If you can, check out Crochet. It wraps up most of the mess involved in
making this work, and vastly simpliies the experience..
http://crochet.readthedocs.org/en/latest/
David
On Tue, Feb 03, 2015 at 03:41:17PM +0100, Abdelhalim Kadi wrote:
> Hello;
>
>
> When i run reactor from thread in
Hey Tobias,
Individual OS have their own mechanisms for avoiding the kind of waste
you're describing. For example, Linux quite aggressively rounds up the
expiry of certain classes of timer at progressively less granular
intervals the further in the future they're scheduled ("timer
coalescing").
W
On Sun, Aug 10, 2014 at 02:51:02PM -0700, Tobias Oberstein wrote:
> But the coalescing you describe would also apply to those implicit
> timers (created from select(timeout = ..) within the Linux kernel)?
It applies to all kernel timers not created by realtime processes.
> This is all fine. But
On Sun, Aug 10, 2014 at 03:31:11PM -0700, Tobias Oberstein wrote:
> Thanks a lot for those hints! I will read into this material.
Just a final note.. a single no-fds call to select with a 0 timeout
seems to take around 280ns on my Core 2. Presumably the better
interfaces (e.g. epoll, but not poll
