Hello,
It does not work. Done: stress-ng (fifo 50), ptp4l (fifo 99),
phc2sys(fifo 99), kworker of the cores where ptp4l and phc2sys run (fifo
99). it still breaks the ptp4l synchronization when stress-ng boots up.
I do not believe that it has not happend to others.
Some new advice?
Thank you for reading,
Diego
El 07/04/2021 a las 17:04, Richard Cochran escribió:
On Wed, Apr 07, 2021 at 11:38:55AM +0200, Diego García Prieto wrote:
I would like to know if I can stablish somehow a deadline to the ptp4l
protocol to avoid other threads run before it. I think that whereby I can
avoid the loss of syncronization. What do you think with respect to it?
IOW, give it higher sched_fifo priority than stress-ng.
Also, depending on your network load, watch out for stress-ng starving
the networking stack (by keeping ksoftirqd from running).
Also, watch out for stress-ng starving kworker threads (if your MAC
driver uses kwork to deliver Tx time stamps).
HTH,
Richard
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
