[PATCHSET v2 cgroup/for-3.17] cgroup: distinguish the default and legacy hierarchies when handling cftypes

From: Tejun Heo
Date: Mon Jul 14 2014 - 11:44:24 EST


This is v2 of dfl_files patchset. Changes from the last version [1]

* Rebased on top of cgroup/for-3.17.

* 0004 updated so that CFTYPE_ONLY_ON_DFL and CFTYPE_INSANE are
cleared when cfts are removed as suggested by Li.

Until now, cftype arrays carried files for both the default and legacy
hierarchies and the files which needed to be used on only one of them
were flagged with either CFTYPE_ONLY_ON_DFL or CFTYPE_INSANE. This
gets confusing very quickly and we may end up exposing interface files
to the default hierarchy without thinking it through.

This patchset makes cgroup core provide separate sets of interfaces
for cftype handling so that the cftypes for the default and legacy
hierarchies are clearly distinguished. This makes all the existing
subsystem interface files legacy-only by default and all subsystems
will have no interface file created when enabled on the default
hierarchy. Each subsystem should explicitly review and compose the
interface for the default hierarchy.

This patchset contains the following six patches.


This patchset is on top of afd1a8b3e0bc ("cpuset: export effective
masks to userspace")

and available in the following git branch.

git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git review-dfl_files-v2

diffstat follows. Thanks.

Documentation/cgroups/unified-hierarchy.txt | 18 ++-
block/blk-cgroup.c | 5
include/linux/cgroup.h | 17 ++
kernel/cgroup.c | 160 +++++++++++++++++++++-------
kernel/cgroup_freezer.c | 2
kernel/cpuset.c | 2
kernel/sched/core.c | 2
kernel/sched/cpuacct.c | 2
mm/hugetlb_cgroup.c | 5
mm/memcontrol.c | 6 -
net/core/netclassid_cgroup.c | 2
net/core/netprio_cgroup.c | 2
net/ipv4/tcp_memcontrol.c | 2
security/device_cgroup.c | 2
14 files changed, 160 insertions(+), 67 deletions(-)


[1] http://lkml.kernel.org/g/1404345055-8196-1-git-send-email-tj@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/