linux-kernel - Re: [PATCH V2] cpuset: Add knob to make allowed masks hotplug invariant on legacy hierarchy

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: <552E47A2.2000909@linux.vnet.ibm.com>
Date:	Wed, 15 Apr 2015 16:42:34 +0530
From:	Preeti U Murthy <preeti@...ux.vnet.ibm.com>
To:	Tejun Heo <tj@...nel.org>
CC:	svaidy@...ux.vnet.ibm.com, peterz@...radead.org,
	nacc@...ux.vnet.ibm.com, rjw@...ysocki.net,
	linux-kernel@...r.kernel.org, lizefan@...wei.com, anton@...ba.org,
	bharata@...ux.vnet.ibm.com, cgroups@...r.kernel.org,
	paulmck@...ux.vnet.ibm.com, mingo@...nel.org, serge@...lyn.com
Subject: Re: [PATCH V2] cpuset: Add knob to make allowed masks hotplug invariant
 on legacy hierarchy

On 04/13/2015 08:20 PM, Tejun Heo wrote:
> On Fri, Apr 10, 2015 at 07:41:52PM +0530, Preeti U Murthy wrote:
>> Moreover the default hierarchy keeps the allowed masks hotplug invariant
>> too. So the patch is not bringing about a fundamental change in the
>> design of cgroups.
> 
> This is gonna be a new behavior anyway and I don't follow why you just
> can't use the default hierarchy (well, of course except for that it
> isn't ready yet but no matter what we do this is gonna take another
> devel cycle so what's the difference?).  It's not like the default

Is it possible today to mount a specific controller on the default
hierarchy ? Or will this capability be going in the next merge window ?
I see that there are  no mount options except the __SANE__ one that the
default hierarchy takes.

We could mount the rest of the controllers in the legacy hierarchy while
mounting the cpuset controller alone in the default hierarchy and see if
this works fine.

Regards
Preeti U Murthy

> hierarchy requires invasive changes.  I'm not convinced this calls for
> yet another operation mode.
> 
> Thanks.
> 

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