Re: 2.6.15:kernel/time.c: The Nanosecond and code duplication

["Ulrich Windl" <ulrich.windl@rz.uni-regensburg.de>]

On 13 Feb 2006 at 11:12, Andi Kleen wrote:

> "Ulrich Windl" <ulrich.windl@rz.uni-regensburg.de> writes:
> 
> > but there's no POSIX like syscall interface 
> > (clock_getres, clock_gettime, clock_settime) yet.
> 
> % grep clock include/asm-x86_64/unistd.h 
> #define __NR_clock_settime      227
> __SYSCALL(__NR_clock_settime, sys_clock_settime)
> #define __NR_clock_gettime      228
> __SYSCALL(__NR_clock_gettime, sys_clock_gettime)
> #define __NR_clock_getres       229
> __SYSCALL(__NR_clock_getres, sys_clock_getres)
> #define __NR_clock_nanosleep    230
> __SYSCALL(__NR_clock_nanosleep, sys_clock_nanosleep)
> 
> Has been available for quite some time.
> 
> However the calls are currently slower than gettimeofday and also
> don't use nanoseconds internally in all cases (depends on the architecture), 
> but still microseconds.  But I'm not sure it matters that much
> because the underlying timers are often not better than microseconds
> anyways and with nanoseconds you start to time even the inherent system
> call latency.

Andi,

thanks! I must have been overlooking the implementation of those. Actually when 
you want to have nanoseconds even if the get_offset() just returns microsecond 
granularity?: If you mathematically correct the clock with nanosecond accuracy (or 
even less). With one model you'll see gradual time change, in the other case 
you'll see jumps of 1000ns. OK, the clock might jump by 100ns for other reasons, 
but currently the clock is so amazingly stable that I hardly believe the results 
I've measured (but that's quite another topic).

I'm fully aware that nanosecond resolution will give us peace for the next years. 
However my 700 MHz Pentium III is already as low as 1µs of jitter, so in theory 
the nanosecond may be worth it (e.g. getting a better estimate of the actual 
jitter).

Regards,
Ulrich

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