linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Rolando Martins <rolando.martins@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cgroup, RT reservation per core(s)?
Date: Tue, 10 Feb 2009 14:06:17 +0100	[thread overview]
Message-ID: <1234271177.23438.24.camel@twins> (raw)
In-Reply-To: <b6a2d2e20902091204p2391799p160ce13971e9f779@mail.gmail.com>

On Mon, 2009-02-09 at 20:04 +0000, Rolando Martins wrote:

> I should have elaborated this more:
> 
>                      root
>                   ----|----
>                   |          |
> (0.5 mem) 0         1 (100% rt, 0.5 mem)
>                          ---------
>                          |    |    |
>                          2   3   4  (33% rt for each group, 33% mem
> per group(0.165))
> Rol


Right, i think this can be done.

You would indeed need cpusets and sched-cgroups.

Split the machine in 2 using cpusets.

   ___R___
  /       \
 A         B

Where R is the root cpuset, and A and B are the siblings.
Assign A one half the cpus, and B the other half.
Disable load-balancing on R.

Then using sched cgroups create the hierarchy

  ____1____
 /    |    \
2     3     4

Where 1 can be the root group if you like.

Assign 1 a utilization limit of 100%, and 2,3 and 4 a utilization limit
of 33% each.

Then place the tasks that get 100% cputime on your 2 cpus in cpuset A
and sched group 1.

Place your other tasks in B,{2-4} respectively.

The reason this works is that bandwidth distribution is sched domain
wide, and by disabling load-balancing on R, you split the schedule
domain.

I've never actually tried anything like this, let me know if it
works ;-)

  reply	other threads:[~2009-02-10 13:04 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 [this message]
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
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=1234271177.23438.24.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rolando.martins@gmail.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;
as well as URLs for NNTP newsgroup(s).