Re: [PATCH] ktimers subsystem 2.6.14-rc2-kt5
From: Roman Zippel
Date: Wed Oct 12 2005 - 17:37:46 EST
On Tue, 11 Oct 2005, Thomas Gleixner wrote:
> > > 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.
> ... 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.
> ...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.
Where does it say anything about that their resolution is equal?
> > > 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.
I know it and above is an _interface_ description, but what leads you to
the conclusion that your _implementation_ is the only correct one?
Thomas, are you even interested in discussing this? Do you just expect
that everyone accepts your patch and is happy? So far it's difficult
enough to get you to explain your design, but a serious discussion also
requires to look at the possible alternatives. It's quite possible I'm
wrong, but you have to try a little harder at explaining why.
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/