Commit 1081312f authored by Michal Hocko's avatar Michal Hocko Committed by Linus Torvalds

memcg: cleanup mem_cgroup_init comment

We should encourage all memcg controller initialization independent on a
specific mem_cgroup to be done here rather than exploit css_alloc
callback and assume that nothing happens before root cgroup is created.
Signed-off-by: default avatarMichal Hocko <mhocko@suse.cz>
Acked-by: default avatarJohannes Weiner <hannes@cmpxchg.org>
Cc: Tejun Heo <htejun@gmail.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent e4777496
...@@ -6830,10 +6830,12 @@ static void __init enable_swap_cgroup(void) ...@@ -6830,10 +6830,12 @@ static void __init enable_swap_cgroup(void)
#endif #endif
/* /*
* The rest of init is performed during ->css_alloc() for root css which * subsys_initcall() for memory controller.
* happens before initcalls. hotcpu_notifier() can't be done together as *
* it would introduce circular locking by adding cgroup_lock -> cpu hotplug * Some parts like hotcpu_notifier() have to be initialized from this context
* dependency. Do it from a subsys_initcall(). * because of lock dependencies (cgroup_lock -> cpu hotplug) but basically
* everything that doesn't depend on a specific mem_cgroup structure should
* be initialized from here.
*/ */
static int __init mem_cgroup_init(void) static int __init mem_cgroup_init(void)
{ {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment