Re: [PATCH] plugsched - update Kconfig-1

From: Peter Williams
Date: Sun Nov 13 2005 - 17:54:27 EST


Con Kolivas wrote:
On Sun, 13 Nov 2005 20:10, Peter Williams wrote:

Con Kolivas wrote:

On Sun, 13 Nov 2005 16:22, Peter Williams wrote:

Con Kolivas wrote:

On Sun, 13 Nov 2005 12:34, Peter Williams wrote:

1. Make the ability to select which schedulers are built in independent
of EMBEDDED.
2. Only offer builtin schedulers as choice for the default scheduler.
3. Only build in ingosched if PLUGSCHED is not configured.

I disagree with 3. Surely people might want to build in only one
scheduler that is not ingosched without other choices.

Yes, and they would be able to do that by selecting PLUGSCHED and then
selecting only the scheduler that they want. But this then leads to the
observation that PLUGSCHED is probably makes things unnecessarily
complex and all that is required is a means to select the schedulers to
be built in and a choice of default (much like for the IO schedulers)?

Indeed it may be better to remove the "plugsched" option entirely. Once
patched in it's not like you are building the kernel without the
plugsched infrastructure. Provided each extra scheduler does not increase
the kernel size too much (and a test build with/without all schedulers
should tell you that), it may be best to just have the scheduler choice
in the top menu and only expose the "schedulers to build in" under
embedded.

I can't see why this should be restricted to embedded systems?


It's just convention that size options go in there; it's not really just for embedded systems.

OK. I guess I'm sometimes guilty of taking things too literally :-(

I'll read up on Kconfig again before I make any changes.

Thanks
Peter
--
Peter Williams pwil3058@xxxxxxxxxxxxxx

"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/