From: "Paul Menage" <menage@google.com>
To: "Paul Jackson" <pj@sgi.com>
Cc: "Felix Obenhuber" <felix@obenhuber.de>,
linux-kernel@vger.kernel.org,
dynsched-devel@lists.sourceforge.net
Subject: Re: [RFC] dynsched - different cpu schedulers per cpuset
Date: Thu, 30 Nov 2006 00:08:36 -0800 [thread overview]
Message-ID: <6599ad830611300008n329ca4a5s133ac62a35bb8d06@mail.gmail.com> (raw)
In-Reply-To: <20061129201310.54da1618.pj@sgi.com>
On 11/29/06, Paul Jackson <pj@sgi.com> wrote:
>
> Your dynamic scheduler mechanisms appear (from what I can tell after a
> brief glance) to be a candidate for being such a controller.
Possibly, if it was some kind of multi-level scheduler - i.e. a
top-level scheduler picks which container to run, and then a
configurable per-container scheduler picks a task from that container.
But (having glanced at the code even less than you) it sounded like it
was intended to be a single level scheduler, configured on a per-cpu
basis. In that case tying it to (exclusive) cpusets sounds like it
might be more reasonable.
Paul.
next prev parent reply other threads:[~2006-11-30 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 16:06 Felix Obenhuber
2006-11-30 4:13 ` Paul Jackson
2006-11-30 4:48 ` Paul Jackson
2006-11-30 8:08 ` Paul Menage [this message]
2006-11-30 19:40 ` Felix Obenhuber
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=6599ad830611300008n329ca4a5s133ac62a35bb8d06@mail.gmail.com \
--to=menage@google.com \
--cc=dynsched-devel@lists.sourceforge.net \
--cc=felix@obenhuber.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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
all inboxes | Powered by JetHome®