Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

memcg: cleanup mem_cgroup_init comment

Browse source 
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: Michal Hocko <mhocko@suse.cz>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Cc: Tejun Heo <htejun@gmail.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
Michal Hocko 2013-02-22 16:35:41 -08:00 committed by Linus Torvalds
parent e477749624
commit 1081312f95
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
mm/memcontrol.c
View file

@ -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)
{ {