I'm looking for tips for optimally configuring ptp4l in a SyncE-enabled network.
Consider the following architecture - the grandmaster's clock and the PTP clock in my slave's NIC share the same frequency source via SyncE. The end goal is to synchronize my slave's Linux system time to the grandmaster. Configuration thoughts: - It seems to me that ptp4l should only examine the time offset between the master and slave, and not try to estimate or correct for differences in frequency. I couldn't find a setting for this, and it seems like frequency estimation is baked pretty deeply into the existing control algorithms. - It seems reasonable to always step the NIC clock rather than slew its frequency. I guess I'd configure that by setting an extremely small step threshold. phc2sys would still slew the system clock to preserve system clock monotonicity (as an aside, I really wish that Linux split the concepts of 'how long a second is' from 'what time is it now' so that the latter could be slewed independently) - Since this is a SyncE network, maybe the error introduced by having ptp4l try to estimate frequency will be low enough to not matter, and so maybe I don't need to do any special configuration. I'd appreciate any thoughts. Does anyone have any pointers to documentation or any analysis on how SyncE and 1588 should work together in general? Thanks! ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
