Hello we are using the xenomai-forge implementation. We from time to time see an issue that the timer-internal thread is consuming a complete core. It is seen when we send broadcast traffic that needs to be handled by the Linux kernel (ARP).
The kernel thread's priority handling the packets in the middle between the timer-internal thread and the application thread's priority. All threads run on the same core. If the priority of the timer-internal is lowered below the kernel thread, the load disappears immediately. So it looks like there is some busy polling on a common resource that is currently held by the application thread running at the lowest prio. I see that the timer lock being used is a mutex with priority inheritance so I would expect that the prio of the application is raised as soon as the timer-internal thread tries to obtain the mutex. It might be that it has nothing to do with the mutex, this is just my guess. Has anybody seen similar issues before? Best regards, Ronny _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
