Hi Miroslav, Thanks for your response. Please find my comments inline below.
The accuracy of which clock would you like to measure? The system clock or the PTP clock on the NIC? We want to measure the accuracy of the PTP clock now. But eventually, we would need to measure the accuracy of the system clock as well. Could you suggest reliable ways to measure both? A separate and more accurate time source is necessary. For measuring the accuracy of SW timestamping you can use HW timestamping. What do you mean by this? Do we need to have PTP enabled NICs to be able to test software timestamping? Not sure if we understand this point correctly. Could you elaborate a bit? Thanks, Dolly On Thu, Oct 25, 2018 at 12:23 AM Richard Cochran <richardcoch...@gmail.com> wrote: > On Wed, Oct 24, 2018 at 02:14:44PM +0530, Dolly Gyanchandani wrote: > > Our current measure of accuracy is based on* master-slave offsets > reported > > by the ptp4l process.* > > Log output, please. > > > *In Hardware Timestamping, *we are getting* >1000 nanoseconds* offset > from > > the master which is far larger than the *expected value of around 50 ns* > of > > PTP H/W Timestamping. > > That is really bad. > > > (Since we do not have a grand-master currently, we are using Master's > > system clock as the Master clock for phc2sys) > > First try leaving the PHC time on the NIC free running. > > Thanks, > Richard >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
