From: "Paul Menage" <menage@google.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: balbir@linux.vnet.ibm.com,
"Andrew Morton" <akpm@linux-foundation.org>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
hugh@veritas.com, xemul@openvz.org, shiwh@cn.fujitsu.com,
mel@csn.ul.ie, linux-kernel@vger.kernel.org
Subject: Re: -mm merge plans for 2.6.26 (memcgroup)
Date: Mon, 21 Apr 2008 08:48:30 -0700 [thread overview]
Message-ID: <6599ad830804210848v754a3aaex6b963dc2e12327fd@mail.gmail.com> (raw)
In-Reply-To: <1208770925.7115.167.camel@twins>
On Mon, Apr 21, 2008 at 2:42 AM, Peter Zijlstra <peterz@infradead.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
next prev parent reply other threads:[~2008-04-21 15:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 14:20 -mm merge plans for 2.6.26 Andrew Morton
2008-04-20 15:51 ` Jiri Slaby
2008-04-20 23:51 ` -mm merge plans for 2.6.26 (memcgroup) Hugh Dickins
2008-04-21 0:30 ` KAMEZAWA Hiroyuki
2008-04-21 6:24 ` Andrew Morton
[not found] ` <480C347C.6060702@linux.vnet.ibm.com>
2008-04-21 6:47 ` Balbir Singh
2008-04-21 9:42 ` Peter Zijlstra
2008-04-21 10:21 ` Balbir Singh
2008-04-21 10:40 ` KAMEZAWA Hiroyuki
2008-04-21 15:48 ` Paul Menage [this message]
2008-04-21 11:22 ` Hugh Dickins
2008-04-21 11:41 ` Andi Kleen
2008-04-21 12:13 ` Hugh Dickins
2008-04-21 13:31 ` kamezawa.hiroyu
2008-04-21 11:41 ` Balbir Singh
2008-05-17 0:03 ` -mm merge plans for 2.6.26 Randy Dunlap
2008-05-17 0:28 ` Andrew Morton
2008-05-17 2:07 ` Randy Dunlap
2008-05-17 4:30 ` Randy Dunlap
2008-05-19 20:26 ` Randy Dunlap
2008-05-19 20:38 ` Andrew Morton
2008-05-19 20:44 ` Sam Ravnborg
2008-05-23 8:05 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6599ad830804210848v754a3aaex6b963dc2e12327fd@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=peterz@infradead.org \
--cc=shiwh@cn.fujitsu.com \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®