Dave Hart h...@ntp.org writes:
I did a bit of searching but of course this is an odd request: help
me degrade the precision of my system clock, please hasn't come up
much. If you have any suggestions, please speak up here, or privately
if you prefer.
On FreeBSD you could try selecting the
Miroslav Lichvar wrote:
Why not degrade the resolution of the clock directly in ntp sources?
Good idea.
In get_systime():
GET_SYSTIME_AS_TIMESPEC(ts);
ts.tv_nsec /= 100;
ts.tv_nsec *= 100;
Ouch!
I'd far prefer a simple mask, getting rid of the bottom N
On 12/17/2011 12:57 PM, David Malone wrote:
Dave Harth...@ntp.org writes:
I did a bit of searching but of course this is an odd request: help
me degrade the precision of my system clock, please hasn't come up
much. If you have any suggestions, please speak up here, or privately
if you
On Thu, Dec 15, 2011 at 07:50:08PM +, Dave Hart wrote:
Dr. Mills raised the possibility privately that either FreeBSD or
Linux might be reconfigured to use a more primitive clock that steps
once per millisecond or less. If possible and I am able to accomplish
it, my testing of these bug
E-Mail Sent to this address will be added to the BlackLists wrote:
Dave Hart wrote:
Linux might be reconfigured to use a more primitive clock that steps
once per millisecond or less.
Linux Kernel 2.4 used 100 Hz and 2.6 increased it to 1000 Hz?
They still read the time to the full CTC
I have some pending changes to improve the way ntpd fuzzes the
insignificant bits of times it reads from the OS clock what that OS
clock ticks slowly enough that it is possible for ntpd to read the
same current time in subsequent gettimeofday()getclock() calls. See
http://bugs.ntp.org/2037.
Dave Hart wrote:
Linux might be reconfigured to use a more primitive clock that steps
once per millisecond or less.
Linux Kernel 2.4 used 100 Hz and 2.6 increased it to 1000 Hz?
Seems like related research / testing
http://wwwagss.informatik.uni-kl.de/Projekte/Squirrel/da/node5.html
--
