From: Glauber Costa <glommer@parallels.com>
To: cgroups@vger.kernel.org
Cc: linux-mm@kvack.org, kamezawa.hiroyu@jp.fujitsu.com,
Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Glauber Costa <glommer@parallels.com>, Tejun Heo <tj@kernel.org>
Subject: [PATCH 2/2] memcg: first step towards hierarchical controller
Date: Tue, 26 Jun 2012 19:47:14 +0400 [thread overview]
Message-ID: <1340725634-9017-3-git-send-email-glommer@parallels.com> (raw)
In-Reply-To: <1340725634-9017-1-git-send-email-glommer@parallels.com>
Okay, so after recent discussions, I am proposing the following
patch. It won't remove hierarchy, or anything like that. Just default
to true in the root cgroup, and print a warning once if you try
to set it back to 0.
I am not adding it to feature-removal-schedule.txt because I don't
view it as a consensus. Rather, changing the default would allow us
to give it a time around in the open, and see if people complain
and what we can learn about that.
Signed-off-by: Glauber Costa <glommer@parallels.com>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
CC: Michal Hocko <mhocko@suse.cz>
CC: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
CC: Tejun Heo <tj@kernel.org>
---
mm/memcontrol.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 85f7790..c37e4c1 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -3993,6 +3993,10 @@ static int mem_cgroup_hierarchy_write(struct cgroup *cont, struct cftype *cft,
if (memcg->use_hierarchy == val)
goto out;
+ WARN_ONCE(!parent_memcg && memcg->use_hierarchy,
+ "Non-hierarchical memcg is considered for deprecation\n"
+ "Please consider reorganizing your tree to work with hierarchical accounting\n"
+ "If you have any reason not to, let us know at cgroups@vger.kernel.org\n");
/*
* If parent's use_hierarchy is set, we can't make any modifications
* in the child subtrees. If it is unset, then the change can
@@ -5221,6 +5225,7 @@ mem_cgroup_create(struct cgroup *cont)
INIT_WORK(&stock->work, drain_local_stock);
}
hotcpu_notifier(memcg_cpu_hotplug_callback, 0);
+ memcg->use_hierarchy = true;
} else {
parent = mem_cgroup_from_cont(cont->parent);
memcg->use_hierarchy = parent->use_hierarchy;
--
1.7.10.2
--
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:[~2012-06-26 15:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 15:47 [PATCH 0/2] fix and deprecate use_hierarchy file Glauber Costa
2012-06-26 15:47 ` [PATCH 1/2] fix bad behavior in " Glauber Costa
2012-06-26 15:52 ` Michal Hocko
2012-06-26 15:54 ` Johannes Weiner
2012-06-26 22:25 ` Andrew Morton
2012-06-26 22:30 ` Tejun Heo
2012-06-26 15:47 ` Glauber Costa [this message]
2012-06-26 16:15 ` [PATCH 2/2] memcg: first step towards hierarchical controller Michal Hocko
2012-06-26 16:37 ` Glauber Costa
2012-06-26 17:54 ` Michal Hocko
2012-06-26 18:04 ` Tejun Heo
2012-06-26 18:55 ` Johannes Weiner
2012-06-26 19:14 ` Tejun Heo
2012-06-26 20:59 ` Johannes Weiner
2012-06-26 21:19 ` Tejun Heo
2012-06-27 8:57 ` Glauber Costa
2012-06-27 17:07 ` Tejun Heo
2012-06-26 22:08 ` Michal Hocko
2012-06-26 22:14 ` Tejun Heo
2012-06-26 22:17 ` Tejun Heo
2012-06-27 8:52 ` Glauber Costa
2012-06-27 16:58 ` Tejun Heo
2012-06-27 12:51 ` Michal Hocko
2012-06-27 12:49 ` Glauber Costa
2012-06-27 17:33 ` Tejun Heo
2012-06-28 8:46 ` Kamezawa Hiroyuki
2012-06-28 9:12 ` Glauber Costa
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=1340725634-9017-3-git-send-email-glommer@parallels.com \
--to=glommer@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=tj@kernel.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