Messages in this thread | | | Date | Tue, 4 Feb 2014 17:10:24 +0100 (CET) | From | Thomas Gleixner <> | Subject | Re: [PATCH v2 0/3] Deferrable timers support for timerfd API |
| |
On Mon, 27 Jan 2014, Alexey Perevalov wrote: > On 01/21/2014 11:12 PM, John Stultz wrote: > > > > Thomas: Any thought here? Should we be trying to unify the timerfd flags > > and the posix timer flags (specifically things like TIMER_CANCEL_ON_SET, > > which is currently timerfd-only)? Should a deferrable flag be added to > > the hrtimer core or left to the timer wheel?
The timer cancel on set was added only to timerfd because timerfd is a non posix interface and we are halfways free to add stuff to it. Adding extra flags to the real posix timer interfaces is a different story.
What's the rationale for a deferrable flag for user space interfaces?
Thanks,
tglx
| |