| |||||||||||
|
| |||||||||||
timerfd() and system call reviewtimerfd() and system call reviewPosted Aug 16, 2007 12:43 UTC (Thu) by IkeTo (subscriber, #2122)In reply to: timerfd() and system call review by nix Parent article: timerfd() and system call review
> but it's a lot easier to write the userspace code
But when "userspace code" means library code, this is going to be hard to sell. After all the application developer see none of those. Can you imagine a version of, say, GLib implements its event loop using the timerfd() interface? Personally I can't.
(Log in to post comments)
timerfd() and system call review Posted Aug 30, 2007 23:19 UTC (Thu) by nix (subscriber, #2304) [Link] Actually I'd expect this to be mostly used by libraries. Currentlylibraries have the problem that signal disposition is process-global and can't be reset without interfering with other libraries, which is ameliorated by signalfd. Also, major libraries like glib *can* realistically include system-dependent code without being too annoying: it only has to go into glib, rather than into all its users (and glib already supports some Linux-specific interfaces anyway: indeed in a sense that's part of its raison d'etre).
|
|||||||||||