sleepy_penguin provides access to newer, Linux-only system calls to wait
on events from traditionally non-I/O sources. Bindings to the eventfd,
timerfd, inotify, signalfd and epoll interfaces are provided.
Here is an idea, not sure if you’d like to pick it up because it would
mean extra work for you.
But, I was wondering… this could be a nice small tutorial which could
teach some more people about both ruby and the new Linux API at the same
time. It is all decently documented but it is also the first time I have
heard of it.
Here is an idea, not sure if you’d like to pick it up because it would
mean extra work for you.
But, I was wondering… this could be a nice small tutorial which could
teach some more people about both ruby and the new Linux API at the same
time. It is all decently documented but it is also the first time I have
heard of it.
Heh, I haven’t used it myself much (nor most of the things I publish).
I suppose most of the test cases are reasonable, maybe I’ll use TimerFD
in an upcoming release of raindrops[1] somewhere…
I suppose most of the test cases are reasonable, maybe I’ll use TimerFD
in an upcoming release of raindrops[1] somewhere…
I just pushed the following change out to raindrops.git. Not the
most useful example, but I like timerfd much more than timer_*
in POSIX (not sure if there are Ruby bindings for those, but in
many cases Kernel#sleep is perfectly adequate
From b0be66c37bb7080b0f06ab76b0e7d3404e2f9059 Mon Sep 17 00:00:00 2001
From: Eric W. [email protected]
Date: Mon, 14 Mar 2011 14:58:40 -0700
Subject: [PATCH] linux-listener-stats: use timerfd if available
It is more accurate than sleep and doesn’t require calculating
times