From: Peter Williams <pwil3058@bigpond.net.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, Al Boldi <a1426z@gawab.com>
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.3.1 for 2.6.16-rc5
Date: Tue, 04 Apr 2006 11:29:54 +1000 [thread overview]
Message-ID: <4431CC12.8060707@bigpond.net.au> (raw)
In-Reply-To: <200604041012.04591.kernel@kolivas.org>
Con Kolivas wrote:
> On Tuesday 04 April 2006 10:01, Peter Williams wrote:
>> Con Kolivas wrote:
>>> On Tuesday 04 April 2006 09:04, Peter Williams wrote:
>>>> Al Boldi wrote:
>>>>> Also, different schedulers per cpu could be rather useful.
>>>>> Peter Williams wrote:
>>>> I think that would be dangerous. However, different schedulers per
>>>> cpuset might make sense but it involve a fair bit of work.
>>> I'm curious. How do you think different schedulers per cpu would be
>>> useful?
>> I don't but I think they MIGHT make sense for cpusets e.g. one set with
>> a scheduler targeted at interactive tasks and another targeted at server
>> tasks. NB the emphasis on might.
>
> I am curious as to Al's answer since he asked for the feature.
OK.
> It would be
> easy for me to modify the staircase cpu scheduler to allow the interactive
> and compute modes be set on a per-cpu basis if that was desired. For that to
> be helpful of course you'd have to manually set affinity for the tasks or
> logins you wanted to run on each cpu(s).
Yes, I agree that it would not be a good idea for CPUs that are sharing
(via load balancing) the same set of tasks to have different schedulers
or policy which is why I suggested only doing it at the cpuset level.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2006-04-04 1:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 11:59 [ANNOUNCE][RFC] PlugSched-6.3.1 for 2.6.16-rc5 Al Boldi
2006-04-03 12:13 ` Paolo Ornati
2006-04-03 23:04 ` Peter Williams
2006-04-03 23:29 ` Con Kolivas
2006-04-04 0:01 ` Peter Williams
2006-04-04 0:12 ` Con Kolivas
2006-04-04 1:29 ` Peter Williams [this message]
2006-04-04 13:27 ` Al Boldi
2006-04-04 13:27 ` Al Boldi
2006-04-04 23:17 ` Peter Williams
2006-04-05 8:16 ` Al Boldi
2006-04-05 22:53 ` Peter Williams
2006-04-07 21:32 ` Al Boldi
2006-04-08 1:29 ` Peter Williams
2006-04-08 20:31 ` Al Boldi
2006-04-09 2:58 ` Peter Williams
2006-04-09 5:04 ` Al Boldi
2006-04-09 23:53 ` Peter Williams
2006-04-10 14:43 ` Al Boldi
2006-04-11 2:07 ` Peter Williams
2006-04-03 23:27 ` Peter Williams
2006-04-04 13:27 ` Al Boldi
2006-04-04 23:20 ` Peter Williams
2006-04-05 8:16 ` Al Boldi
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 22:32 Peter Williams
2006-03-01 2:36 ` Peter Williams
2006-04-02 2:04 ` Peter Williams
2006-04-02 6:02 ` Con Kolivas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4431CC12.8060707@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=a1426z@gawab.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox