Thanks.
>> /* get timestamp after triggering since RAND_bytes is slow */ > When I added that comment I found that RAND_bytes() was taking hundreds of > nanoseconds on the same system that was taking the classic version's local > random less than 100ns. When I saw that comment, I thought that getting the time had been moved from someplace else. There is (was?) at least one driver that gives you a time stamp when a signal changes and that signal wired to a modem pin. A reverse PPS. Between "triggering" and "since", I was looking for something interesting. > I revisited that area when the --disable-fuzz option was added in order to > experiment with also removing fuzzing from the refclocks. I got a very > significant reduction in jitter when switching from get_systime() to > clock_gettime(). Did you try get_systime() and --disable-fuzz? That should do the same thing. -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
