| Re: [chrony-users] makestep in Chrony |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Tue, May 15, 2018 at 05:57:04AM +0000, Hei Chan wrote:
> If I remember correctly that there was a post explaining why it wasn't a bug, the post mentioned the value was written to a shared memory (or some sort), and the writer and reader aren't protected by a lock for performance reason, and so it needs to spin (i.e while loop) to get the value out as soon as the writer finishes.
How do you avoid this issue in your solution? If you update the
estimated frequency offset between real time and tsc, you will need to
prevent the conversion from using partially updated values. If you
don't update the offset at all (estimated only once on start), the
tsc-based clock will drift away.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.