Hello Richard, On 19 Feb 2014, at 12:23, Richard Cochran <richardcoch...@gmail.com> wrote: > On Wed, Feb 19, 2014 at 10:40:11AM +0100, Delio Brignoli wrote: >> >> Preventing the port from being labelled asCapable and avoid calculating >> neighborRateRatio is exactly what I want to do. I am working with specs >> layered on top of 802.1AS-2011 which require me to flag a port as >> non-asCapable if the peer delay is negative. > > If you think this is the right behavior for gPTP, then we can make it > work that way always (without an option). > > Something like this?
[…] I spent some time yesterday reading the relevant bits of the 802.1AS standard and I agree with you: the gPTP standard does not forbid negative peer delay. In fact, as long as neighborRateRatio can be calculated (i.e. neighborRateRatioValid is true) then asCapable should be true (assuming all other unrelated conditions are met). So I would implement this as an config option which defaults to ‘no lower limit' for peer delay. If you are OK with this I will send an updated patch (probably later today). Thanks! — Delio ------------------------------------------------------------------------------ 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
