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?
if (p->pod.follow_up_info && pd < 0) {
pr_warning("negative peer delay %10lld", pd);
pr_warning("peer_delay = ((t4 - t1) - (t3 - t2) - (c1 +
c2))/2");
pr_warning("t3 - t2 = %+10lld", t3 - t2);
pr_warning("t4 - t1 = %+10lld", t4 - t1);
pr_warning("c1 %10lld", c1);
pr_warning("c2 %10lld", c2);
return;
}
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
