On Wed, 29 Nov 2023 at 15:45, Paz Cohen <[email protected]> wrote:
> I have noticed that "delay_timeout" returned by pmc with > "PORT_SERVICE_STATS_NP" is always increasing, even when rx delay responses > are arriving as expected. > It appears to happen because code flow does not get to resetting the delay > timeout(FD_DELAY_TIMER), unless poll woke on this fd. The problem is that > the delay_timeout counter is incremented together with the timer resetting. > What I expected is that when a legitimate delay response arrives, the > timer should reset. > This is a developers mailing list. You are welcome to find the error and send a patch to fix it. > If I understand the behavior correctly, then delay response timeouts > cannot be detected by pmc. > PMC is not a detection tool. It just retrieves information from the ptp4l service. If you find a "wrong" value, it probably comes from the ptp4l service itself. Erez > > BR, > Paz > _______________________________________________ > Linuxptp-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/linuxptp-devel >
_______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
