On Wed, Jun 07, 2017 at 06:20:40PM +0000, Rodney Greenstreet wrote: > I think this SM is optimized for behaving as you suggest, with the > assumption all sync intervals are the same. However, a port’s > syncInterval, or some fraction of it, must be adhered to. Also, if a > Sync event is not received within a syncInterval for a given port, > that port will still transition to ‘SEND_MD_SYNC’ and send a Sync > event.
IOW, the received Sync message is forwarded immediately, provided that it arrives no sooner than syncInterval/2 after the previous message. The important fact is that the time window is relative to the last received Sync message, not to some arbitrary internal timer. Maybe you aren't aware of it, but prior to the publication of 802.1AS, the AVB group published results demonstrating improved synchronization performance when forwarding the Sync ASAP. Your patch completely misses this central point, and as such does not implement a Time Aware Bridge according to 802.1AS. Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
