Re: [RFC][PATCH] new timeofday core subsystem (v.A0)

From: George Anzinger
Date: Fri Sep 03 2004 - 02:32:24 EST


Albert Cahalan wrote:
On Thu, 2004-09-02 at 21:39, George Anzinger wrote:

john stultz wrote:


+
+static nsec_t jiffies_cyc2ns(cycle_t cyc, cycle_t* remainder)
+{
+
+ cyc *= NSEC_PER_SEC/HZ;

Hm... This assumes that 1/HZ is what is needed here. Today this value is 999898. Not exactly reachable by NSEC_PER_SEC/HZ. Or did I miss something, like the relationship of jiffie to 1/HZ and to real time.


HZ not being HZ is the source of many foul problems.

NTP should be able to correct for the error. For systems
not running NTP, provide a fake NTP to make corrections
based on the expected frequency error.

Based on that, skip or double-up on the ticks to make
them be exactly HZ over long periods of time.

There are several problems here. First, to make this possible, you will have to outlaw several values for HZ (1024 comes to mind). Second, like it or not, 1/HZ or something close to it, is the timer resolution. I think we need to try and keep this a power of 10, mostly because there are a lot of folks who just don't understand it if it is not. And third, you need to get real close to it with the hardware timer. If you introduce NTP or some such to fix things, well, things just break another place. For example, we started 2.6 with HZ=1000 and had problems like:
> time sleep 10
sleeping for 9.9 seconds. This will just not do. Any corrections made to the wall clock really need to be made to the timer system as well. As it is we assume that, by correctly choosing the tick value, the wall clock will be correct on average, even under NTP. I.e. that the NTP correction will be, over time, very small. We really do want code that is much more accurate than "time sleep 10" to be right, i.e. if we sleep for x nanoseconds, the wall clock will have changed by x nanoseconds while we did so.



~

--
George Anzinger george@xxxxxxxxxx
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml

-
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/