[ntp:questions] Re: clock resolutions for different OS

Ulrich Windl Ulrich.Windl at RZ.Uni-Regensburg.DE
Thu Aug 28 06:55:05 UTC 2003

What do you want? Is using the "jitter.c program from the NTP sources
not sufficient to get your machine's clock resolution? Resolution
depends on system load, believe me. Even dirty-ing the CPU's cache may
affect timing (ia32).


ryandrk at hotmail.com (Drk Ryan) writes:

> I can find in the MSDN documentation where the 10ms figure for WinNT
> is stated.
> But if I want to see where it is documented that a stock FreeBSD
> kernel handles nanoseconds while Linux handles microseconds where do I
> look to find these values? The microtime page of the freeBSD manual
> contains no actual values.
> > 
> > "Drk Ryan" <ryandrk at hotmail.com> wrote in message
> > news:de98eac0.0308191107.b6e68be at posting.google.com...
> > > Since operating systems such as Linux, Solaris, certain versions of
> > > Unix, and WinNT all run at 100Hz clock resolution how is it that their
> > > timimg suppport varies: FreeBSD handles nanoseconds, Linux handles
> > > microseconds and WinNT only ~10 milliseconds?
> > >
> > > As 1/100Hz = 10ms should they all not return a resolution of 10ms?

More information about the questions mailing list