SO_TIMESTAMPING [1] is a socket option for obtaining transmit and receive
timestamps. ntpd uses SO_TIMESTAMP to get receive timestamps. Transmit
timestamps require NIC driver support [2] and the application gets the
timestamp after the packet is sent.
A PTP-like protocol is used to measure the del
On Thursday, October 18, 2012 5:53:02 PM UTC+8, gabs wrote:
> Sample measurements (raw):
> left: delay
> right: offset (in microseconds)
>
> 91509 509
> 89577 -991
> 88365 -795
> 89574 -731
> 90593 -163
> 89360 -1067
>
> 92650 -318
> 90634 -910
> 89455 -989
> 89511 -1080
> 88874 -693
> 88534 -11
On Thu, Oct 18, 2012 at 02:53:02AM -0700, gabs wrote:
> SO_TIMESTAMPING [1] is a socket option for obtaining transmit and receive
> timestamps. ntpd uses SO_TIMESTAMP to get receive timestamps. Transmit
> timestamps require NIC driver support [2] and the application gets the
> timestamp after the p
On Thursday, October 18, 2012 6:40:01 PM UTC+8, Miroslav Lichvar wrote:
>
> NTP supports interleaved mode in peer associations which does the
> timestamp followup. It would be really nice if ntpd supported the
> SO_TIMESTAMPING option.
>
> http://www.eecis.udel.edu/~mills/ntp/html/xleave.html
>
