Re: Extending socket timestamping API for NTP

2017-02-09 Thread sdncurious
> >> > 5) new SO_TIMESTAMPING options to get transposed RX timestamps >> > >> >PTP uses preamble RX timestamps, but NTP works with trailer RX >> >timestamps. This means NTP implementations currently need to >> >transpose HW RX timestamps. The calculation requires the link speed >> >

Re: Extending socket timestamping API for NTP

2017-02-08 Thread sdncurious
On Wed, Feb 8, 2017 at 2:26 AM, Miroslav Lichvar wrote: > On Tue, Feb 07, 2017 at 12:37:15PM -0800, sdncurious wrote: >> On Tue, Feb 7, 2017 at 6:01 AM, Miroslav Lichvar wrote: >> > 6) new SO_TIMESTAMPING option to get PHC index with HW timestamps >> > >> >

Re: Extending socket timestamping API for NTP

2017-02-08 Thread sdncurious
paths. This often occurs if one way is via landline and the other via satellite. It can also occur when the paths traverse tag-switched core networks. RMS On Wed, Feb 8, 2017 at 2:26 AM, Miroslav Lichvar wrote: > On Tue, Feb 07, 2017 at 12:37:15PM -0800, sdncurious wrote: >> On Tue, Feb 7

Re: Extending socket timestamping API for NTP

2017-02-07 Thread sdncurious
On Tue, Feb 7, 2017 at 6:01 AM, Miroslav Lichvar wrote: > 5) new SO_TIMESTAMPING options to get transposed RX timestamps > >PTP uses preamble RX timestamps, but NTP works with trailer RX >timestamps. This means NTP implementations currently need to >transpose HW RX timestamps. The ca