From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Rolando Martins <rolando.martins@gmail.com>,
linux-kernel@vger.kernel.org, Paul Menage <menage@google.com>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Subject: Re: cgroup, RT reservation per core(s)?
Date: Wed, 11 Feb 2009 17:23:57 +0530 [thread overview]
Message-ID: <20090211115357.GG16317@balbir.in.ibm.com> (raw)
In-Reply-To: <1234352534.23438.130.camel@twins>
* Peter Zijlstra <peterz@infradead.org> [2009-02-11 12:42:14]:
> On Wed, 2009-02-11 at 11:33 +0000, Rolando Martins wrote:
>
> > Hi again,
> >
> > is there any way to have multiple "distinct" sched domains, i.e.:
> > mount -t cgroup -o cpu none /dev/sched_domain_0
> > .... setup sched_domain_0 (ex: 90% RT, 10% Others)
> > mount -t cgroup -o cpu none /dev/sched_domain_1
> > .... setup sched_domain_1 (ex: 20% RT, 80% Others)
> > Then give sched_domain_0 to cpuset A and sched_domain_1 to B?
>
> Nope.
>
> We currently only support a single instance of a cgroup controller.
>
> I see the use for what you propose, however implementing that will be
> 'interesting'.
I am confused, if you cpusets, you get your own sched_domain. If you
mount cpusets and cpu controller together, you'll get what you want.
Is this a figment of my imagination. You might need to use exclusive
CPUsets though.
--
Balbir
next prev parent reply other threads:[~2009-02-11 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 19:30 cgroup, RT reservation per core(s)? Rolando Martins
2009-02-09 19:52 ` Peter Zijlstra
2009-02-09 20:04 ` Rolando Martins
2009-02-10 13:06 ` Peter Zijlstra
2009-02-10 14:46 ` Rolando Martins
2009-02-10 16:00 ` Peter Zijlstra
2009-02-10 17:32 ` Rolando Martins
2009-02-10 19:53 ` Peter Zijlstra
2009-02-11 11:33 ` Rolando Martins
2009-02-11 11:42 ` Peter Zijlstra
2009-02-11 11:53 ` Balbir Singh [this message]
2009-02-11 12:00 ` Peter Zijlstra
2009-02-11 12:10 ` Rolando Martins
2009-03-03 12:58 ` Rolando Martins
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=20090211115357.GG16317@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=peterz@infradead.org \
--cc=rolando.martins@gmail.com \
--cc=vatsa@linux.vnet.ibm.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