[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090702020624.14469.47066.stgit@menage.mtv.corp.google.com>
Date: Wed, 01 Jul 2009 19:10:52 -0700
From: Paul Menage <menage@...gle.com>
To: lizf@...fujitsu.com, balbir@...ux.vnet.ibm.com
Cc: linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
containers@...ts.linux-foundation.org,
kamezawa.hiroyu@...fujitsu.com
Subject: [PATCH 0/9] [RFC] CGroup Hierarchy Extensions
The following series adds support for:
- named cgroup hierarchies
- cgroup hierarchies with no bound subsystems
- cgroup subsystems that can be bound to multiple hierarchies
This allows more flexibility when constructing/mounting cgroups
hierarchies, and allows functionality that's not tied to specific
external resources to be made available on multiple cgroups
hierarchies rather than just one.
A few simple example cgroups subsystems that are multi-bindable are
included in the patch series.
---
Paul Menage (9):
[RFC] Support named cgroups hierarchies
[RFC] Move the cgroup debug subsys into cgroup.c to access internal state
[RFC] Add a back-pointer from struct cg_cgroup_link to struct cgroup
[RFC] Allow cgroup hierarchies to be created with no bound subsystems
[RFC] Remove cgroup_subsys.root pointer
[RFC] Remove the cgroup_subsys.bind callback
[RFC] Support multiply-bindable cgroup subsystems
[RFC] Example multi-bindable subsystem: a per-cgroup notes field
[RFC] Example multi-bindable subsystem: a max-depth controller
Documentation/cgroups/cgroups.txt | 8
include/linux/cgroup.h | 55 ++
include/linux/cgroup_subsys.h | 14 +
init/Kconfig | 17 +
kernel/Makefile | 3
kernel/cgroup.c | 905 +++++++++++++++++++++++++++----------
kernel/cgroup_debug.c | 105 ----
kernel/info_cgroup.c | 133 +++++
kernel/maxdepth_cgroup.c | 80 +++
9 files changed, 938 insertions(+), 382 deletions(-)
delete mode 100644 kernel/cgroup_debug.c
create mode 100644 kernel/info_cgroup.c
create mode 100644 kernel/maxdepth_cgroup.c
--
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