On 2019-02-20 08:47:51 [+0100], Juri Lelli wrote: > > In this case you prepare the wakeup and then wake the CPU anyway. There > > should be no downside to this unless the housekeeping CPU is busy and in > > irq-off regions which would increase the latency. Also in case of > > cyclictest -d0 > > > > the one CPU would have to process all timers. So the latency will be > > worse compared to every CPU does its own wakeup. And on RT you probably > > do not want to do deep idle anyway. > > Mmm, right. But, still very much dependent on the workload, I understand > you are saying? So, no one size fits all solution. Now that I slept over it, I think it makes sense from RT point of view to always pin the timer. I'm not sure if we want to swap the sysctl or make the PINNED change like you suggested. > Thanks, > > - Juri Sebastian
