[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <469C08BF.5010406@bigpond.net.au>
Date: Tue, 17 Jul 2007 10:09:35 +1000
From: Peter Williams <pwil3058@...pond.net.au>
To: Ingo Molnar <mingo@...e.hu>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.5.1 for 2.6.22
Ingo Molnar wrote:
> * Peter Williams <pwil3058@...pond.net.au> wrote:
>
>> Probably the last one now that CFS is in the main line :-(.
>
> hm, why is CFS in mainline a problem?
It means a major rewrite of the plugsched interface and I'm not sure
that it's worth it (if CFS works well). However, note that I did say
probably not definitely :-). I'll play with it and see what happens.
> The CFS merge should make the life
> of development/test patches like plugsched conceptually easier. (it will
> certainly cause a lot of churn, but that's for the better i think.)
I don't think that is necessarily the case.
>
> Most of the schedulers in plugsched should be readily adaptable to the
> modular scheduling-policy scheme of the upstream scheduler.
I don't think that this necessarily true. Ingosched and ingo_ll are
definitely out and I don't feel like converting staircase and nicksched
as I have no real interest in them. Perhaps I'll just create the
interface and some schedulers based on my own ideas and let others such
as Con and Nick add schedulers if they're still that way inclined.
> I'm sure
> there will be some minor issues as isolation of the modules is not
> enforced right now - and i'd be happy to review (and potentially apply)
> common-sense patches that improve the framework.
Thanks for the offer of support (it may sway my decision),
Peter
--
Peter Williams pwil3058@...pond.net.au
"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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists