[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F670DC2.1030904@parallels.com>
Date: Mon, 19 Mar 2012 14:43:14 +0400
From: Glauber Costa <glommer@...allels.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
CC: Tejun Heo <tj@...nel.org>, <lizf@...fujitsu.com>,
<containers@...ts.linux-foundation.org>, <cgroups@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <fweisbec@...il.com>,
<rni@...gle.com>, <ctalbott@...gle.com>,
Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...e.cz>,
Balbir Singh <bsingharora@...il.com>,
Hugh Dickins <hughd@...gle.com>,
Greg Thelen <gthelen@...gle.com>
Subject: Re: [PATCH 06/10] cgroup: convert memcg controller to the new cftype
interface
On 03/19/2012 08:26 AM, KAMEZAWA Hiroyuki wrote:
>> ->populate() is preserved for register_kmem_files() invocation but I
>> > strongly urge moving the initialization to the tail of ->create(). If
>> > there's something which can't be done from ->create(), which isn't
>> > clear from the comment, please let me know.
>> >
> Okay, then, cgroup files are created in kernel/cgroup.c and memcg just
> registers entries.
>
>
>
I am still in the middle of the review. Is it possible to dynamically
register entries? (right now, I mean)
If yes - which seems to be a bit of the point of the exercise, so it
should be totally okay from my PoV. I have that call in populate because
which files will be created depends on which protocols you have registered.
The trick here, is that doesn't need to happen at all cgroup creations.
But it can't happen at root's either, because this is quite fragile:
some protocols may only be registered after root memcg is created.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists