On Tue, Jul 12, 2016 at 10:36:29PM +0800, W.F. YANG wrote: > Richard， > Here i got a minor suspect issue: > Role: slave node > Delay Mechanism: E2E > Scenario: slave sent a delay_req to master, and duration period of > issuing delay_req for next time is determined by set_tmo_random(), it is a > random value. If the slave node send the delay_req again prior to > receiving the first delay_resp from master, the first delay_resp will be > discarded due to having previous sequence number
This is the expected behavior. The timing of the delay request messages does not depend on the reponse from the master. (Consider what would happen if the master never responds...) Thanks, Richard ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
