From: Glauber Costa <glommer@parallels.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michal Hocko <mhocko@suse.cz>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] memcg: first step towards hierarchical controller
Date: Tue, 26 Jun 2012 19:31:21 +0400 [thread overview]
Message-ID: <4FE9D5C9.805@parallels.com> (raw)
In-Reply-To: <20120626141127.GA27816@cmpxchg.org>
On 06/26/2012 06:11 PM, Johannes Weiner wrote:
> I find the warning message a bit terse. Maybe include something like
> "restructure the cgroup directory structure to match your accounting
> requirements or complain to (linux-mm, cgroups list etc.) if not
> possible"
How about:
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");
--
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:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 13:30 Glauber Costa
2012-06-26 14:11 ` Johannes Weiner
2012-06-26 14:19 ` Peter Zijlstra
2012-06-26 14:38 ` Johannes Weiner
2012-06-26 14:38 ` Glauber Costa
2012-06-26 14:41 ` Peter Zijlstra
2012-06-26 14:29 ` Glauber Costa
2012-06-26 15:31 ` Glauber Costa [this message]
2012-06-26 15:37 ` Johannes Weiner
2012-06-26 15:27 ` Michal Hocko
2012-06-26 15:28 ` Glauber Costa
2012-06-26 15:50 ` Michal Hocko
2012-06-26 18:12 ` Tejun Heo
2012-06-26 18:22 ` Glauber Costa
2012-06-26 18:32 ` Tejun Heo
2012-06-26 22:12 ` Michal Hocko
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=4FE9D5C9.805@parallels.com \
--to=glommer@parallels.com \
--cc=a.p.zijlstra@chello.nl \
--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