Re: [chrony-dev] SW/HW timestamping on Linux

2016-11-24 Thread Miroslav Lichvar
On Wed, Nov 23, 2016 at 03:24:56PM -0800, Denny Page wrote: > I am now seeing better standard deviations with hardware timestamping than > software timestamping. Thank you. > > Couple of caveats: > - I need to disable priority scheduling (-P). With priority scheduling, > software stamps still

Re: [chrony-dev] SW/HW timestamping on Linux

2016-11-24 Thread Denny Page
I do not have xleave enabled. Can you explain more as to why you would expect to see such an offset without xleave? Thanks, Denny > On Nov 24, 2016, at 05:11, Miroslav Lichvar wrote: > > That suggests the interleaved mode is not working. Are the peers specified > with the xleave option? -- T

Re: [chrony-dev] SW/HW timestamping on Linux

2016-11-24 Thread Miroslav Lichvar
On Thu, Nov 24, 2016 at 06:46:36AM -0800, Denny Page wrote: > I do not have xleave enabled. Can you explain more as to why you would expect > to see such an offset without xleave? The offset is calculated from four timestamps. Two local and two remote. Without xleave the peer can't deliver the TX

Re: [chrony-dev] SW/HW timestamping on Linux

2016-11-24 Thread Denny Page
This makes sense. Thank you. I will enable xleave and retest shortly. Denny > On Nov 24, 2016, at 06:57, Miroslav Lichvar wrote: > > On Thu, Nov 24, 2016 at 06:46:36AM -0800, Denny Page wrote: >> I do not have xleave enabled. Can you explain more as to why you would >> expect to see such an o