One thing. Try to load the CPU with stress-ng in your systems and check
what happens.
This is the stress-ng command: "sudo stress-ng --cpu 4 --cpu-load 25
--sched fifo --sched-prio 50 --times"
This command generates 4 threads (because I want to add load to my 4
cores) with 25% of load each. It use a FIFO scheduler with priority 50.
Remember that my ptp4l and phc2sys processes are with priority FIFO 99.
Notice that the issue rises up when one stress-ng thread shares the same
core than ptp4l. Besides, this happens when the scheduler is Round Robin
or FIFO. Without any of them, there is no issues.
I ask this to check is this also happens to all of you.
If you need more information about this issue, just ask me.
Thank you,
Diego G.
El 22/04/2021 a las 11:58, Diego García Prieto escribió:
Hello Richard,
El 22/04/2021 a las 2:03, Richard Cochran escribió:
On Wed, Apr 21, 2021 at 09:55:31PM +0000, Keller, Jacob E wrote:
You mentioned you were using igb. I believe that driver still relies
on a work queue task to handle the Tx timestamps, as well as
overflow check.
Right, and work has no priority at all in the kernel. This could be
improved at the driver level by using the PHC kthread, which then
could be given priority administratively.
Could you explain it in other words? Do you see something to improve?
Do not hesitate to reply as many times as you want.
Thank you very much for your help.
Diego G.
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
