Well on high load, you shouldn't have an idle cpu anyway, so you would never
pass the requirements for the agressive -idle- steal even if it was turned
on. On low loads on HT, without this agressive balance on cpu bound tasks,
you will always load up one core before using any of the others. When you
fork/exec, the child will start on the same runqueue as the parent, the idle
sibling will start running it, and it will never get a chance to balance
properly while it's in a run state. This is the same behavior I saw with the
NUMA-HT solution, because I didn't have this agressive balance (although it
could be added I suppose), and as a result it consistently performed less
than Ingo's solution (but still better than no patch at all).
-Andrew Theurer
-
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/