linux-kernel - Re: cgroup, RT reservation per core(s)?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1234209174.5951.165.camel@laptop>
Date:	Mon, 09 Feb 2009 20:52:54 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Rolando Martins <rolando.martins@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: cgroup, RT reservation per core(s)?

On Mon, 2009-02-09 at 19:30 +0000, Rolando Martins wrote:
> Hi,
> I would like to have in a quad-core, 2 cores totally (100%) dedicated
> to RT tasks (SCHED_RR and SCHED_FIFO) and the other 2 cores with
> normal behavior, better said,  allowing SCHED_OTHER & SCHED_FIFO &
> SCHED_RR tasks but still with a RT reservation. Follows an example:
> 
> 
> # Setup first domain (cpu 0,1)
> echo 0-1 > /dev/cgroup/0/cpuset.cpus
> echo 0 > /dev/cgroup/0/cpuset.mems
> 
> # Setup RT bandwidth for firstdomain (80% for RT, 20% others)
> echo 1000000 > /dev/cgroup/0/cpu.rt_period_us
> echo 800000 > /dev/cgroup/0/cpu.rt_runtime_us
> 
> 
> # Setup second domain (cpu 2,3)
> mkdir /dev/cgroup/1
> echo 2-3 > /dev/cgroup/1/cpuset.cpus
> echo 0 > /dev/cgroup/1/cpuset.mems
> 
> # Setup RT bandwidth for second domain (100% for RT)
> echo 1000000 > /dev/cgroup/1/cpu.rt_period_us
> echo 1000000 > /dev/cgroup/1/cpu.rt_runtime_us
> 
> Is there anyway for doing this?

Nope, but why do you need bandwidth groups if all you want is a full
cpu?

Just the cpuset should be plenty

--
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/