|| ||Balbir Singh <firstname.lastname@example.org>|
|| ||[RFC][mm][PATCH 0/4] Memory cgroup hierarchy introduction (v2)|
|| ||Sat, 08 Nov 2008 14:40:09 +0530|
|| ||YAMAMOTO Takashi <email@example.com>,
Paul Menage <firstname.lastname@example.org>, email@example.com,
Nick Piggin <firstname.lastname@example.org>,
David Rientjes <email@example.com>,
Pavel Emelianov <firstname.lastname@example.org>,
Dhaval Giani <email@example.com>,
Balbir Singh <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
KAMEZAWA Hiroyuki <firstname.lastname@example.org>|
|| ||Article, Thread
This patch follows several iterations of the memory controller hierarchy
patches. The hardwall approach by Kamezawa-San. Version 1 of this patchset
The current approach is based on  and has the following properties
1. Hierarchies are very natural in a filesystem like the cgroup filesystem.
A multi-tree hierarchy has been supported for a long time in filesystems.
When the feature is turned on, we honor hierarchies such that the root
accounts for resource usage of all children and limits can be set at
any point in the hierarchy. Any memory cgroup is limited by limits
along the hierarchy. The total usage of all children of a node cannot
exceed the limit of the node.
2. The hierarchy feature is selectable and off by default
3. Hierarchies are expensive and the trade off is depth versus performance.
Hierarchies can also be completely turned off.
The patches are against 2.6.28-rc2-mm1 and were tested in a KVM instance
with SMP and swap turned on.
Signed-off-by: Balbir Singh <email@example.com>
1. The hierarchy is now selectable per-subtree
2. The features file has been renamed to use_hierarchy
3. Reclaim now holds cgroup lock and the reclaim does recursive walk and reclaim
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/