On Wed, Jun 07, 2017 at 06:11:42PM +0200, Richard Cochran wrote:
> On Wed, Jun 07, 2017 at 02:46:39PM +0000, Rodney Greenstreet wrote:
> > Based on these clauses, it’s clear that each port maintains its own
> > sync interval setting and needs to maintain its own sync interval
> > timer. It’s also clear that when the slave port of a TAB receives a
> > sync event, that message is not immediately sent out on downstream
> > ports. Rather, the configured sync interval for a given port must be
> > adhered to.
>
> Consider clause B.2.2. There the residence time is limited to 10
> milliseconds at maximum. Using an internal timer to forward the Sync
> message would violate this requirement.
Better yet, look at Figure 10-2 on page 46.
The flow of an incoming Sync message is:
MDSyncReceive 11.2.13
PortSyncSyncReceive 10.2.7
SiteSyncSync 10.2.6
PortSyncSyncSend 10.2.11
MDSyncSend 11.2.14
If you follow the state machines, you will see that the Sync message
is forwarded without delay in every case. The *only* place that the
syncInterval is considered is in PortSyncSyncSend, but there it is
used as a timeout value.
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
