On Wed, 2012-09-26 at 11:19 -0700, Linus Torvalds wrote: > > For example, it starts with the maximum target scheduling domain, and > works its way in over the scheduling groups within that domain. What > the f*ck is the logic of that kind of crazy thing? It never makes > sense to look at a biggest domain first.
That's about SMT, it was felt that you don't want SMT siblings first because typically SMT siblings are somewhat under-powered compared to actual cores. Also, the whole scheduler topology thing doesn't have L2/L3 domains, it only has the LLC domain, if you want more we'll need to fix that. For now its a fixed: SMT MC (llc) CPU (package/machine-for-!numa) NUMA So in your patch, your for_each_domain() loop will really only do the SMT/MC levels and prefer an SMT sibling over an idle core. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
