On Fri, Feb 21, 2014 at 01:01:04PM +0100, Delio Brignoli wrote: > > No, it can hardly be as low in practice but I was actually thinking the > opposite: we should increase neighborPropDelayThresh to INT32_MAX. I mean, > why the half hearted attempt at disabling the option when we can ensure it > never triggers? Also 20ms is really a number I came up with because is large > enough, but it’s not specified anywhere.
I think the defaults only have to be reasonable, not perfect. IMHO, twenty milliseconds is a nice value because almost certainly PTP won't work at that level, but still a misconfigured network might produce this value. So it acts as a safety net, like the clockcheck code. Thanks, Richard ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
