jacob.e.kel...@intel.com said: > We get into the kthread function within a few hundred usec or less, and then > the firmware read takes a long time, sometimes over 2 milliseconds.
Why is it taking so long? How long does it take when things go well? Is there anything complicated going on with a "firmware read"? Is there a software lock, maybe because some other code is using related hardware resources? Is the thread not getting scheduled? ------- My first try was rejected by the list software because I sent it from the wrong address. -- These are my opinions. I hate spam. _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
