adjtimex and clock resolutions

bizoo · 09-01-2009, 10:28 AM

HI

I was just looking at ntp daemon and adjtimex functions. I saw that adjtimex can only correct offsets in microsecond range.
HOWEVER, with hrtimers these days, we easily have nanosecond resolution timers, so why cant we get rid of nanosecond offsets using adjtimex and avoid losing accuracy
??

Also, is there any way of using the nanosecond range difference with adjtimex or any other utility?

thanks
cheers!

neonsignal · 09-07-2009, 05:19 AM

There were patches for the 2.4 kernels to provide pulse per second support and a nanosecond interface.

There are also current projects that provide pulse per second support for the 2.6 kernels.

This is only useful if you have a synchronizing time source accurate to nanoseconds (not just precise to nanoseconds), such as a GPS sourced interrupt.

archtoad6 · 09-08-2009, 09:45 AM

Quote:

Originally Posted by neonsignal

This is only useful if you have a synchronizing time source accurate to nanoseconds (not just precise to nanoseconds), such as a GPS sourced interrupt.

Excellent point -- to help readers understand the difference: Accuracy and precision