Re: [PATCH] ktimers subsystem 2.6.14-rc2-kt5

[Thomas Gleixner <tglx@linutronix.de>]

On Mon, 2005-10-10 at 19:22 +0200, Roman Zippel wrote:
> > The above gives a clear distinction between scalar and sec/nsec based
> > cases. So you cannot mess up without notice. 
> 
> There are enough macros to do this anyway. There are a number of 
> operations which are identical. Separating them artifically makes 
> everything only more complicated.

I don't see a distinct set of macros around which is providing all the
functionality.

> > As far as I understand SUS timer resolution is equal to clock resolution
> > and the timer value/interval is rounded up to the resolution.
> 
> Please check the rationale about clocks and timers. It talks about clocks 
> and timer services based on them and their resolutions can be different.

clock_settime():
... Time values that are between two consecutive non-negative integer
multiples of the resolution of the specified clock shall be truncated
down to the smaller multiple of the resolution.

timer_settime():
...Time values that are between two consecutive non-negative integer
multiples of the resolution of the specified timer shall be rounded up
to the larger multiple of the resolution. Quantization error shall not
cause the timer to expire earlier than the rounded time value.

> > Reprogramming interval timers by now + interval is completely wrong.
> > Reprogramming has to be 
> > timer->expires + interval and nothing else. 
> 
> Where do get the requirement for an explicit rounding from?
> The point is that the timer should not expire early, but there is more 
> than one way to do this and can be done implicitly using the timer 
> resolution.

See above.

tglx