From: Tejun Heo <tj@kernel.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Glauber Costa <glommer@parallels.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
kamezawa.hiroyu@jp.fujitsu.com, Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] memcg: first step towards hierarchical controller
Date: Tue, 26 Jun 2012 12:14:50 -0700 [thread overview]
Message-ID: <20120626191450.GT3869@google.com> (raw)
In-Reply-To: <20120626185542.GE27816@cmpxchg.org>
Hello, Johannes.
On Tue, Jun 26, 2012 at 08:55:42PM +0200, Johannes Weiner wrote:
> > 2. Mark flat hierarchy deprecated and produce a warning message if
> > memcg is mounted w/o hierarchy option for a year or two.
>
> I think most of us assume that the common case is either not nesting
> directories or still working with hierarchy support actually enabled.
How do we know that? At least from what I see from blkcg usage,
people do crazy stuff when given crazy interface and we've been
providing completely crazy interface for years. We cannot switch that
implicitly - the changed default behavior is drastically different and
even could be difficult to chase down. Transitions towards good
behavior are good but they have to be explicit.
> I would hate if people had to jump through hoops to get the only
> behaviour we want to end up supporting and to not get yelled at, it
> sends all the wrong signals.
It is inconvenient but that's the price that we have to pay for having
been stupid. Kernel flipping behavior implicitly is far worse than
any such inconvenience.
These default behavior flips are something is better handled by
distros / admins than kernel itself. They can orchestrate the
userland infrastructure and handle and communicate these flips far
better than kernel alone can do. We can't send out mails to flat
hierarchy users after all. That's the reason why I'm suggesting mount
option which can't be flipped (sans remount but that's going away too)
once the system is configured by the distro or admin.
The kernel should nudge mainline users towards new behavior while
providing distros / admins a way to move to the new behavior. The
kernel itself can't flip it like that.
> > 3. After the existing users had enough chance to move away from flat
> > hierarchy, rip out flat hierarchy code and error if hierarchy
> > option is not specified.
>
> This description sounds much more sane than what we are actually
> trying to ban, which is not a flat structure, but treating groups with
> nested directories as equal siblings.
Ah... yeah, flat hierarchy probably is the wrong way to describe it.
I don't know. Superficial hierarchy?
Thanks.
--
tejun
--
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 19:14 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 ` [PATCH 2/2] memcg: first step towards hierarchical controller Glauber Costa
2012-06-26 16:15 ` 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 [this message]
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=20120626191450.GT3869@google.com \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=glommer@parallels.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).