Re: timerfd syscall

[Anupam Kapoor <anupam.kapoor@xxxxxxxxx>]

Michael Kerrisk <mtk> wrote:
On Mon, Apr 28, 2008 at 7:12 AM, Anupam Kapoor <anupam.kapoor@xxxxxxxxx> wrote:
,----
| > one simple question though: should'nt it be possible to simulate the
| > interface provided by timerfd using a combination of signalfd +
| > getitimer ?
| 
| Each timer delivers its notification on a different file descriptor.
| We can't do that using signalfd + a traditional timer mechanism.  (By
| the way setitimer wouldn't come close -- you can only have one
| wall-clock timer set via that API -- POSIX timers allow multiple
| timers...)
`----
yes {get,set}itimer provide only a single timer / process. posix timers
aka timer_create and friends do allow for multiple timers /
process. 

but, with posix-timers too, it seems that the number is limited by the
current number of outstanding signals for a process (this seems to be
RLIMIT_SIGPENDING which is '11' on x86, after a quick glance, so i might
be wrong). 

i guess, with the new timer api, this would not be an issue (except
ofcourse a limit on max-open-fd's / process which can always be
changed) ?

thanks
anupam

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ