[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20121002074407.GD6144@localhost>
Date: Tue, 2 Oct 2012 16:44:07 +0900
From: Tejun Heo <tj@...nel.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, Michal Hocko <mhocko@...e.cz>,
Johannes Weiner <hannes@...xchg.org>,
Balbir Singh <bsingharora@...il.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
cgroups@...r.kernel.org, linux-mm@...ck.org,
Li Zefan <lizefan@...wei.com>
Subject: [GIT PULL] cgroup hierarchy changes for v3.7-rc1
Hello,
This is another v3.7-rc1 pull request for cgroup. Currently,
different cgroup subsystems handle nested cgroups completely
differently. There's no consistency among subsystems and the
behaviors often are outright broken.
People at least seem to agree that the broken hierarhcy behaviors need
to be weeded out if any progress is gonna be made on this front and
that the fallouts from deprecating the broken behaviors should be
acceptable especially given that the current behaviors don't make much
sense when nested.
This patch makes cgroup emit warning messages if cgroups for
subsystems with broken hierarchy behavior are nested to prepare for
fixing them in the future. This was put in a separate branch because
more related changes were expected (didn't make it this round) and the
memory cgroup wanted to pull in this and make changes on top.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-3.7-hierarchy
Thanks.
Tejun Heo (1):
cgroup: mark subsystems with broken hierarchy support and whine if cgroups are nested for them
block/blk-cgroup.c | 8 ++++++++
include/linux/cgroup.h | 15 +++++++++++++++
kernel/cgroup.c | 12 +++++++++++-
kernel/cgroup_freezer.c | 8 ++++++++
kernel/events/core.c | 7 +++++++
mm/memcontrol.c | 7 +++++++
net/core/netprio_cgroup.c | 12 +++++++++++-
net/sched/cls_cgroup.c | 9 +++++++++
security/device_cgroup.c | 9 +++++++++
9 files changed, 85 insertions(+), 2 deletions(-)
--
tejun
--
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