linux-kernel - Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector

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]

Date:	Thu, 06 Nov 2008 12:31:24 +0530
From:	Balbir Singh <balbir@...ux.vnet.ibm.com>
To:	Paul Menage <menage@...gle.com>
CC:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	linux-mm@...ck.org, YAMAMOTO Takashi <yamamoto@...inux.co.jp>,
	lizf@...fujitsu.com, linux-kernel@...r.kernel.org,
	Nick Piggin <nickpiggin@...oo.com.au>,
	David Rientjes <rientjes@...gle.com>,
	Pavel Emelianov <xemul@...nvz.org>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Srivatsa Vaddagiri <vatsa@...ibm.com>
Subject: Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector

Balbir Singh wrote:
> Paul Menage wrote:
>> On Sun, Nov 2, 2008 at 7:52 AM, Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
>>> That should not be hard, but having it per-subtree sounds a little complex in
>>> terms of exploiting from the end-user perspective and from symmetry perspective
>>> (the CPU cgroup controller provides hierarchy control for the full hierarchy).
>>>
>> The difference is that the CPU controller works in terms of shares,
>> whereas memory works in terms of absolute memory size. So it pretty
>> much has to limit the hierarchy to a single tree. Also, I didn't think
>> that you could modify the shares for the root cgroup - what would that
>> mean if so?
>>
> 
> The shares are proportional for the CPU controller. I am confused as to which
> shares (CPU you are talking about?
> 
>> With this patch set as it is now, the root cgroup's lock becomes a
>> global memory allocation/deallocation lock, which seems a bit painful.
> 
> Yes, true, but then that is the cost associated with using a hierarchy.
> 
>> Having a bunch of top-level cgroups each with their own independent
>> memory limits, and allowing sub cgroups of them to be constrained by
>> the parent's memory limit, seems more useful than a single hierarchy
>> connected at the root.
> 
> That is certainly do-able, but can be confusing to users, given how other
> controllers work. We can document that
> 
>> In what realistic circumstances do you actually want to limit the root
>> cgroup's memory usage?
>>
> 
> Good point, I would expect that people would mostly use the hierarchy with
> soft-limits or shares. I am now beginning to like Kamezawa and your suggestion
> of limiting usage to subtrees.

Oh! I am not sure if I mentioned, but you don't need to limit usage at the root.
Any parent along the hierarchy can be limited and it will act as if the entire
subtree is limited by that limit.

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