I would LOVE to use a scheduler tuned for my hardware if outperformed the generic scheduler. I'm not a kernel developer, but I can imagine how the mainstream si

I would LOVE to use a scheduler tuned for my hardware if outperformed the generic scheduler. I'm not a kernel developer, but I can imagine how the mainstream single-socket multicore case may be quite different from the multi-socket multicore case. As I software engineer, I realize that making different schedulers for different architectures is "inefficient" (unless development/test resources are increased). But if somebody is willing to put in the time and effort to make me a scheduler that works best on my hardware, I'll gladly take it. I have to agree with Con's remarks here. Seems like an underhanded move by Ingo to give this thing a bad reputation (and hence kill developer and beta tester interest) before it comes out. And judging by the comments here, he may have succeeded. Looks like open source has lots of politics too. :)