> >> Idle tasks nowdays don't spin waiting for need->resched to change,
> >> they sleep on a halt insn instead. Therefore any setting of
> >> need->resched on an idle task running on a remote CPU should be
> >> accompanied by a cross-processor interrupt.
> >
> > this is broken as well. Check out the idle=poll feature i wrote some time
> > ago.
>
> The idle=poll stuff is a hack. [...]
it's a feature.
> [...] I'd like my idle cpus to sleep and still have them wake up the
> moment work for them becomes available. I see no reason why an idle cpu
> should be forced to remain idle until the next tick, nor why fixing that
> should be considered `broken'.
performance. IPIs are expensive.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/