linux-kernel - Re: -mm merge plans for 2.6.26 (memcgroup)

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] [day] [month] [year] [list]

Message-ID: <6599ad830804210848v754a3aaex6b963dc2e12327fd@mail.gmail.com>
Date:	Mon, 21 Apr 2008 08:48:30 -0700
From:	"Paul Menage" <menage@...gle.com>
To:	"Peter Zijlstra" <peterz@...radead.org>
Cc:	balbir@...ux.vnet.ibm.com,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>,
	hugh@...itas.com, xemul@...nvz.org, shiwh@...fujitsu.com,
	mel@....ul.ie, linux-kernel@...r.kernel.org
Subject: Re: -mm merge plans for 2.6.26 (memcgroup)

On Mon, Apr 21, 2008 at 2:42 AM, Peter Zijlstra <peterz@...radead.org> wrote:
>  > This would enable the memory controller by default, it can be disabled
>  > using cgroup_disable=memory at boot time.
>
>  how about working on a runtime switch that only enables the whole
>  memcgroup machinery when an actual cgroup gets created - and disable it
>  again once the last cgroup goes.
>

Or more specifically, enable memory tracking when the mem controller
gets bound to a cgroup hierarchy, and disable it when the controller
is unbound.

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