Re: [PATCH 0/13] Turn hrtimers into a range capable timer

[Thomas Gleixner]

On Fri, 12 Sep 2008, Rusty Russell wrote:
> On Tuesday 02 September 2008 09:03:43 Arjan van de Ven wrote:
> > This series is a follow-on the the nanosecond select/poll series.
> >
> > The goal of this series is to introduce the capability into hrtimers to
> > deal with a "range" rather than a specific point in time.
> > (Several people discussed this recently, but we've been toying with the
> > concept for a while)
> 
> Hi Arjen, sorry for not replying sooner.
> 
> I had half a patch to create a new "timer layer to rule them all" called 
> ktimers, which took an explicit "slop" value.  Slop is the "how long before 

Be warned, the name ktimers has already a bad history. Just ask the
oracle of google :)

> its worth waking the machine for this?" value, with friendly SLOP_USECS, 
> SLOP_SECONDS, SLOP_DAYS etc defines.  Implemented in terms of normal and hr 
> timers, which get deprecated over time.
> 
> Heuristics work for a while, but IMHO eventually this is going to have to be 
> plumbed through to userspace.

Agreed.

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/