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

On Sat, Nov 12, 2016 at 10:36:55AM -0800, Denny Page wrote: > Here is a reasonable visual representation of what I am seeing. The section > on the left (before 8:00) is with hardware timestamping, while the section on > the right is with software timestamping. maxdelaydevratio of 4 in both

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

On Sat, Nov 12, 2016 at 10:36:55AM -0800, Denny Page wrote: > Here is a reasonable visual representation of what I am seeing. The section > on the left (before 8:00) is with hardware timestamping, while the section on > the right is with software timestamping. maxdelaydevratio of 4 in both

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

Setting noselect for all sources seems to have no impact on standard deviation. Disabling all forms of dynamic tic (CONFIG_HZ_PERIODIC=y) seems to have some effect in reducing the number of “D H”, but does not appear to have much of an impact on the standard deviation. I am returning

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

Yes, I these on the monitoring system. For all servers/peers. Denny > On Nov 14, 2016, at 05:35, Miroslav Lichvar wrote: > > Do you see in measurements.log any entries with 'D K' and > '111 111 ' in the columns with tests results (i.e. were any 'D K' > measurements

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

On Mon, Nov 14, 2016 at 10:47:52AM -0800, Denny Page wrote: > I’m not sure I understand what effect a delay in NIO_Linux_RequestTxTimestamp > would have. That I see, NIO_Linux_RequestTxTimestamp builds a control message > structure but does not make any level 2 calls. Introducing a delay here >