Re: Why the smp version of zephyr kernel "idle" task implent the "k_busy_wait(100)" delay?
FWIW: the reason for the busy wait is to reduce the number of calls to k_yield() which needs to enter the scheduler and obviously take a spinlock for synchronization. If you have one CPU spinning on the scheduler lock, the other is going to constantly have to contend for it and you get a performance disaster.
FWIW: we have an IPI framework now. This is straightforward to fix.
On 8/4/19 5:41 PM, Boie, Andrew P wrote: