Work item list: l_fp_time and l_fp_offset
Hal Murray
hmurray at megapathdsl.net
Wed Apr 26 22:43:00 UTC 2017
> Let's use timestamp and offset.
Good suggestion. Thanks.
> But I'm OK with doubles for offsets. If the offset is into many years the
> nanosec will take care of themselves later.
Ahh. Good.
> So you start with two l_fp, or two timespec(64), or one of each. Then
> subtract to get an offet as a timespec(64) or a double.
My expectation is that timestamps would never leave the front end. The
subtracts and pivot would happen there resulting in an offset.
There is a back door for l_fp and/or timestamps. That's ntpq.
We may have to convert offsets back to l_fp for backward compatibility with
old ntpq.
There may be some timestamps saved that I don't know about. If they are used
for other than ntpq then they will need timespec.
--
These are my opinions. I hate spam.
More information about the devel
mailing list