[Dropping Gary and Jacob from CC, this is not related to the original topic anymore.]
On Wed, 25 Feb 2015 16:15:31 +0100, Miroslav Lichvar wrote: > The man page says the clock is synchronized by another process. It's not clear what that means, though. I think the behavior of ntpshm is so special that it deserves a special chapter in the man page describing how it works, how to use it and that specifying clock sources (including the system clock and the -r parameter) has different meaning with this servo. I mean, even I am very confused by this thing, what about poor users ;-) > > From the user point of view, the shm is just another time > > source. In the code, it could be implemented as a fake clock (as you > > need at least two clocks for phc2sys to do anything) driven by this > > special servo. > > I don't follow. What would the fake clock do? > > > Requiring the user to add a random second clock for this > > to work (be it a system clock or a different PHC) is very confusing. > > It's not a random clock, it's the clock that is synchronized by the > SHM consumer, i.e. the system clock with chronyd/ntpd. SHM samples > contain timestamps from both clocks (PHC and system clock). Hmm, I see. The fake clock would not help, then. I still don't like it but I don't see a better way to do this, currently. We definitely need a better documentation. Thanks for the explanation, Jiri -- Jiri Benc ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
