> No, that description only holds for what are called "coarse" clocks.
Do you understand this area?
I think the term I've been missing is "dither". I don't understand that area
well enough to explain it to anybody. Interesting timing. I was at a talk a
few weeks ago that covered dithering.
> Also the PLL goes up and offsets rise. (just like before)
Another way to maybe learn something.
Can you grab a copy of
http://users.megapathdsl.net/~hmurray/time-nuts/60Hz/60Hz.py
It's a hack to measure line frequency using the PPS capture logic. The idea
is to turn that inside out and
> HPET is a travel out to ACPI system registers mapped into memory, this should
> never be never cached.
Yes. But there is still the cache for code and data.
This sort of code is amazingly delicate. Minor changes can make interesting
changes in the results.
For example:
for (i = 0; i <
Hal Murray via devel writes:
> devel@ntpsec.org said:
>> That's a fantastically wierd distribution. Here's what my old single core
>> Athlon64 does:
>
> Your sample is what I would expect from a system that isn't doing much. If
> there is other activity going on, the clean bell curve gets
devel@ntpsec.org said:
> That's a fantastically wierd distribution. Here's what my old single core
> Athlon64 does:
Your sample is what I would expect from a system that isn't doing much. If
there is other activity going on, the clean bell curve gets spread out due to
cache reloads and
Udo van den Heuvel via devel writes:
> hpet:
That's a fantastically wierd distribution. Here's what my old single
core Athlon64 does:
--8<---cut here---start->8---
ntpsec/attic> ./clocks
res avg min dups CLOCK
1 1498 977
On 14-04-19 14:01, Hal Murray wrote:
> backwards runs forever. ^C when you get bored.
No output after running `backwards` for over 30 minutes.
Udo
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
On 14-04-19 14:01, Hal Murray wrote:
> I just pushed some tweaks. Would you please try attic/clock and
hpet:
# ./a.out
res avg min dups CLOCK
1 1666 419CLOCK_REALTIME
400 5 444-1 CLOCK_REALTIME_COARSE
1 1657 419
On 14-04-19 14:01, Hal Murray wrote:
>
> udo...@xs4all.nl said:
>> ntpsec 1.1.3's ntpd from
>> ftp://ftp.ntpsec.org/pub/releases/ntpsec-1.1.3.tar.gz
>> gives me after startup:
>
>> Apr 13 15:53:50 bla ntpd[12382]: CLOCK: ts_prev 1555163630 s + 594156272 ns,
>> ts_min 1555163630 s + 594155713
udo...@xs4all.nl said:
> ntpsec 1.1.3's ntpd from ftp://ftp.ntpsec.org/pub/releases/ntpsec-1.1.3.tar.gz
> gives me after startup:
> Apr 13 15:53:50 bla ntpd[12382]: CLOCK: ts_prev 1555163630 s + 594156272 ns,
> ts_min 1555163630 s + 594155713 ns
...
Thanks.
So now we know it wasn't a recent
10 matches
Mail list logo
