On Thu, Aug 05, 2021 at 06:44:00AM -0700, Richard Cochran wrote: > On Thu, Aug 05, 2021 at 06:40:35AM -0700, Richard Cochran wrote: > > Of course you are welcome to hack it into ptp4l for your research. > > And once you have the AI algorithm perfected, simply code the result > into the device driver as Jacob suggested.
I'm not sure if it's written anywhere or enforced, but there is an expectation that from the clock's point of view RX timestamps should never be before start of the reception and TX timestamps should never be later than start of the transmission. If this algorithm that is being researched cannot keep the error on the right side, I think it shouldn't be implemented in the driver, or at least it should be disabled by default, as it would break assumptions in applications that try to estimate the maximum error (e.g. NTP). I'd prefer to keep things like that in the application, or maybe as a library, if it could be useful to multiple applications. Is this about mlx5 NICs? -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
