Re: [PATCHSET cgroup/for-3.15] cgroup: prepare for the default unified hierarchy
From: Li Zefan
Date: Mon Mar 17 2014 - 23:55:35 EST
On 2014/3/14 3:50, Tejun Heo wrote:
> The planned unified hierarchy is just around the corner. We're gonna
> repurpose the dummy hierarchy to serve as the default unified
> hierarchy. Controllers which aren't attached to other hierarchies are
> already automatically bound to the dummy hierarchy; however, the dummy
> hierarchy is minimally initialized during boot and can't currently act
> as a full hierarchy.
> This patchset gradually turns the dummy hierarchy into fully
> functional default one and makes it mountable via selecting
> sane_behavior without any subsystems specified. While this patchset
> does make the default hierarchy mountable, the unified hierarchy
> functionality isn't implemented yet and cgroup creation in the default
> hierarchy is rejected for now.
> This lays down all the boilerplate work for the unified hierarchy.
> The next patchset will implement the actual unified functionality.
> This patchset contains the following eleven patches.
> 0001-0002 are misc fix / prep.
> 0003-0009 (mostly) turn the dummy hierarchy into a full hierarchy
> which takes on controllers which aren't attached to other hierarchies.
> 0010-0011 make the default hierarchy mountable and implement
> This patchset is on top of cgroup/for-3.15 b8dadcb58d54 ("cpuset: use
> rcu_read_lock() to protect task_cs()"). diffstat follows.
> block/blk-throttle.c | 4
> block/cfq-iosched.c | 4
> include/linux/cgroup.h | 57 ++---
> kernel/cgroup.c | 464 +++++++++++++++++++++++++---------------------
> kernel/cgroup_freezer.c | 2
> kernel/cpuset.c | 2
> mm/hugetlb_cgroup.c | 2
> mm/memcontrol.c | 4
> net/core/netprio_cgroup.c | 2
> net/ipv4/tcp_memcontrol.c | 2
> security/device_cgroup.c | 4
> 11 files changed, 295 insertions(+), 252 deletions(-)
Looks good in general!
Acked-by: Li Zefan <lizefan@xxxxxxxxxx>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/