On Wed, Apr 26, 2023 at 10:43:52AM +0200, Luigi 'Comio' Mantellini wrote: > Hi Miroslav, > > Sync is already sent using a constant interval as required by Standard even > if it is lower than the nominal frequency for the actual implementation > (stop and rearm).
It's not constant. It's randomized by the scheduling of the ptp4l process. If you see two servers sending sync messages at the same time, you can expect their transmissions to slowly drift away from each other. > The sync is forged by master as a one-to-many message that does not > saturate the link, the randomization is required for the messages from > Clients to Master (Delay-Req) in order to avoid congestion on Master. > General messages are randomized also. The same thing needs to be considered for multiple servers in different domains on the same communication path. > Speaking about messages collision in TX path, this is not an issue here > because your HW timestamp will (should) set the correct TS value at the end > of TX queue. On the RX side, the TS is applied just before the RX queue. If all NICs and switches/routers had perfect HW timestamping, I might agree. > As reported by Richard, the conformance is not impacted by the proposed fix. You have still not explained what is the issue you are trying to fix. Is there some specification that requires the average sync interval to be within 0.1% of the logSyncInterval? I hope it's not someone complaining about a test report not having a round number. -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
