yeah, you are probably right when it comes to task migration policy
impact - that can have effects in that range. (and that, you have to
accept, is a fundamentally hard and fragile job to get right, as it
involves observing the past and predicting the future out of it - at
1.3 million events per second)
So above i was just talking about straight scheduling code overhead.
(that cannot have been +10% of the total - as the whole scheduler only
takes 7% total - TLB flush and FPU restore overhead included. Even the
hrtimer bits were about 1% of the total.)
Ingo
--
