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: <20090211115357.GG16317@balbir.in.ibm.com>
Date:	Wed, 11 Feb 2009 17:23:57 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Rolando Martins <rolando.martins@...il.com>,
	linux-kernel@...r.kernel.org, Paul Menage <menage@...gle.com>,
	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
Subject: Re: cgroup, RT reservation per core(s)?

* Peter Zijlstra <peterz@...radead.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
--
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/