On Tue, 13 Aug 2002, Martin J. Bligh wrote:
>
> Right, accepted. But if it's good for P4, and bad for P3 (at least for some
> workloads), surely this leads to the conclusion that it should be a config
> option (probably defaulting to being on)? If you can see another way to
> solve the conundrum ....
But this is exactly the kinds of cases that config options do _not_ work
well for.
There are tons of reasons to run the same kernel on a multitude of
machines, even ignoring the issue of things like installers etc.
We had this CONFIG_xxxx disease when it came to SSE, we had it when it
came to TSC, etc. And in every case it ended up being bad, simply because
it's not the right interface for _users_.
So this is why I think the IRQ balance code has to be there, regardless,
and then it gets turned on dynamically for when it is needed (or turned
off when it hurts, whatever). But it should _not_ be a CONFIG option.
Linus
-
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/
This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:33 EST