From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: linux-mm@kvack.org
Cc: YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Paul Menage <menage@google.com>,
lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
David Rientjes <rientjes@google.com>,
Pavel Emelianov <xemul@openvz.org>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector
Date: Sun, 02 Nov 2008 00:19:02 +0530 [thread overview]
Message-ID: <20081101184902.2575.11443.sendpatchset@balbir-laptop> (raw)
In-Reply-To: <20081101184812.2575.68112.sendpatchset@balbir-laptop>
Don't enable multiple hierarchy support by default. This patch introduces
a features element that can be set to enable the nested depth hierarchy
feature. This feature can only be enabled when there is just one cgroup
(the root cgroup).
Signed-off-by: Balbir Singh <balbir@linux.vnet.ibm.com>
---
mm/memcontrol.c | 38 +++++++++++++++++++++++++++++++++++++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff -puN mm/memcontrol.c~memcg-add-hierarchy-selector mm/memcontrol.c
--- linux-2.6.28-rc2/mm/memcontrol.c~memcg-add-hierarchy-selector 2008-11-02 00:15:00.000000000 +0530
+++ linux-2.6.28-rc2-balbir/mm/memcontrol.c 2008-11-02 00:15:00.000000000 +0530
@@ -40,6 +40,9 @@
struct cgroup_subsys mem_cgroup_subsys __read_mostly;
#define MEM_CGROUP_RECLAIM_RETRIES 5
+static unsigned long mem_cgroup_features;
+#define MEM_CGROUP_FEAT_HIERARCHY 0x1
+
/*
* Statistics for memory cgroup.
*/
@@ -1080,6 +1083,31 @@ out:
return ret;
}
+static u64 mem_cgroup_feature_read(struct cgroup *cont, struct cftype *cft)
+{
+ return mem_cgroup_features;
+}
+
+static int mem_cgroup_feature_write(struct cgroup *cont, struct cftype *cft,
+ u64 val)
+{
+ int retval = 0;
+ struct cgroup *cgroup = init_mem_cgroup.css.cgroup;
+
+ if (val & MEM_CGROUP_FEAT_HIERARCHY) {
+ if (list_empty(&cgroup->children))
+ mem_cgroup_features |= MEM_CGROUP_FEAT_HIERARCHY;
+ else
+ retval = -EBUSY;
+ } else {
+ if (list_empty(&cgroup->children))
+ mem_cgroup_features &= ~MEM_CGROUP_FEAT_HIERARCHY;
+ else
+ retval = -EBUSY;
+ }
+ return retval;
+}
+
static u64 mem_cgroup_read(struct cgroup *cont, struct cftype *cft)
{
return res_counter_read_u64(&mem_cgroup_from_cont(cont)->res,
@@ -1214,6 +1242,11 @@ static struct cftype mem_cgroup_files[]
.name = "stat",
.read_map = mem_control_stat_show,
},
+ {
+ .name = "features",
+ .write_u64 = mem_cgroup_feature_write,
+ .read_u64 = mem_cgroup_feature_read,
+ },
};
static int alloc_mem_cgroup_per_zone_info(struct mem_cgroup *mem, int node)
@@ -1292,7 +1325,10 @@ mem_cgroup_create(struct cgroup_subsys *
return ERR_PTR(-ENOMEM);
}
- res_counter_init(&mem->res, parent ? &parent->res : NULL);
+ if ((mem_cgroup_features & MEM_CGROUP_FEAT_HIERARCHY) && parent)
+ res_counter_init(&mem->res, &parent->res);
+ else
+ res_counter_init(&mem->res, NULL);
for_each_node_state(node, N_POSSIBLE)
if (alloc_mem_cgroup_per_zone_info(mem, node))
_
--
Balbir
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-11-01 18:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 18:48 [mm][PATCH 0/4] Memory cgroup hierarchy introduction Balbir Singh
2008-11-01 18:48 ` [mm] [PATCH 1/4] Memory cgroup hierarchy documentation Balbir Singh
2008-11-04 6:25 ` Paul Menage
2008-11-04 6:26 ` Paul Menage
2008-11-05 13:55 ` Balbir Singh
2008-11-01 18:48 ` [mm] [PATCH 2/4] Memory cgroup resource counters for hierarchy Balbir Singh
2008-11-02 5:42 ` KAMEZAWA Hiroyuki
2008-11-02 5:49 ` Balbir Singh
2008-11-02 5:56 ` KAMEZAWA Hiroyuki
2008-11-02 11:46 ` Balbir Singh
2008-11-01 18:48 ` [mm] [PATCH 3/4] Memory cgroup hierarchical reclaim Balbir Singh
2008-11-02 5:37 ` KAMEZAWA Hiroyuki
2008-11-02 5:44 ` Balbir Singh
2008-11-04 2:17 ` KAMEZAWA Hiroyuki
2008-11-05 13:34 ` Balbir Singh
2008-11-05 16:20 ` KAMEZAWA Hiroyuki
2008-11-06 14:00 ` Balbir Singh
2008-11-01 18:49 ` Balbir Singh [this message]
2008-11-02 5:38 ` [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector KAMEZAWA Hiroyuki
2008-11-02 6:03 ` Balbir Singh
2008-11-02 6:24 ` KAMEZAWA Hiroyuki
2008-11-02 15:52 ` Balbir Singh
2008-11-04 6:37 ` Paul Menage
2008-11-06 7:00 ` Balbir Singh
2008-11-06 7:01 ` Balbir Singh
2008-11-06 6:56 ` Balbir Singh
2008-11-06 7:30 ` KAMEZAWA Hiroyuki
2008-11-04 0:15 ` [mm][PATCH 0/4] Memory cgroup hierarchy introduction KAMEZAWA Hiroyuki
2008-11-05 13:51 ` Balbir Singh
2008-11-05 16:33 ` KAMEZAWA Hiroyuki
2008-11-05 17:52 ` Balbir Singh
2008-11-06 0:22 ` KAMEZAWA Hiroyuki
2008-11-04 9:21 ` [patch 1/2] memcg: hierarchy, yet another one KAMEZAWA Hiroyuki
2008-11-04 9:25 ` KAMEZAWA Hiroyuki
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=20081101184902.2575.11443.sendpatchset@balbir-laptop \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=rientjes@google.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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