Love the move, and will actually try it really soon. Well, at least with your last diff. (;
On Fri, 2009-05-15 at 14:39 +0000, Michael Shalayeff wrote: > re > using floating point for ntpd math is not a good idea. > this comes from the fact that mixing small and large numbers > in one fp expression leads to a huge loss of precision. > besides the fact that there is no need to change representation > from fixed point (ntp timestamps) to floating point and > back all the time. plus to that using fpu in daemons is > not polite and eats even more cpu time (: > > this diff converts internal math to fixed point (64bit) > except for one place -- local clock frequency drift. > this part is still broken as one can see by constantly > flipping frequency adjucements in the logs since math > currently used performs computation on very large > numbers (products of time stamps) and very small > ones (products of time offsets) and thus totally useless. > i have figured a better way to follow frequency drift > but that can be done in the next step. > > this has ran on both i386 and sparc64 for months now > and only has shown massive improvement in precision > (decrease of deviation). thus local clock offset still > flips every few hours from positive to negative and back > due to broken frequency adjucements.
