Work item list: l_fp_time and l_fp_offset

Gary E. Miller gem at
Wed Apr 26 23:12:34 UTC 2017

Yo Hal!

On Wed, 26 Apr 2017 15:43:00 -0700
Hal Murray <hmurray at> wrote:

> > 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.

I'm not gonna guess on where that happens now.  It happens before
local_clock() which is called with an offset and in turn calls
step_systime(), adj_systime(), or ntp_adjtime_ns() with an offset
when it wants to touch the system clock.

So any pivot from local_clock() on down to step_systime(),
adj_systime(), or ntp_adjtime_ns() is pointless.

> 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.

Either orks for me, but back compatibility is good.

> 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.

Just about every refclock has their own way of doing the timestamp.

Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the devel mailing list