mm: memcg: deprecate cgroup v1 non-hierarchical mode
Subsystems (4)
cover mm: memcg: deprecate cgroup v1 non-hierarchical mode
The non-hierarchical cgroup v1 mode is a legacy of early days of the memory controller and doesn't bring any value today. However, it complicates the code and creates many edge cases all over the memory controller code.
It's a good time to deprecate it completely. This patchset removes the internal logic, adjusts the user interface and updates the documentation. The alt patch removes some bits of the cgroup core code, which become obsolete.
From Michal Hocko:
All that we know today is that we have a warning in place to complain loudly when somebody relies on use_hierarchy=0 with a deeper hierarchy. For all those years we have seen _zero_ reports that would describe a sensible usecase.
Moreover we (SUSE) have backported this warning into old distribution kernels (since 3.0 based kernels) to extend the coverage and didn't hear even for users who adopt new kernels only very slowly. The only report we have seen so far was a LTP test suite which doesn't really reflect any real life usecase.
v1:
- added a note from Michal
- added acks and reviews
rfc:
- https://lwn.net/Articles/835983/
Roman Gushchin (3):
mm: memcg: deprecate the non-hierarchical mode
docs: cgroup-v1: reflect the deprecation of the non-hierarchical mode
cgroup: remove obsoleted broken_hierarchy and warned_broken_hierarchy
.../admin-guide/cgroup-v1/memcg_test.rst | 8 +- .../admin-guide/cgroup-v1/memory.rst | 40 +++------ include/linux/cgroup-defs.h | 15 ---- include/linux/memcontrol.h | 7 -- kernel/cgroup/cgroup.c | 12 --- mm/memcontrol.c | 90 +++---------------- 6 files changed, 29 insertions(+), 143 deletions(-)
Signature · 1 line
2.26.2
PATCH 1/3 mm: memcg: deprecate the non-hierarchical mode
The non-hierarchical cgroup v1 mode is a legacy of early days of the memory controller and doesn't bring any value today. However, it complicates the code and creates many edge cases all over the memory controller code.
It's a good time to deprecate it completely.
Functionally this patch enabled is by default for all cgroups and forbids switching it off. Nothing changes if cgroup v2 is used:
hierarchical mode was enforced from scratch.
To protect the ABI memory.use_hierarchy interface is preserved with a limited functionality: reading always returns "1", writing of "1" passes silently, writing of any other value fails with -EINVAL and a warning to dmesg (on the first occasion).
--- include/linux/memcontrol.h | 7 --- kernel/cgroup/cgroup.c | 5 --- mm/memcontrol.c | 90 ++++++-------------------------------- 3 files changed, 13 insertions(+), 89 deletions(-)
include/linux/memcontrol.h +0 -7
@@ -234,11 +234,6 @@ struct mem_cgroup {/* vmpressure notifications */ struct vmpressure vmpressure; -/* -* Should the accounting and control be hierarchical, per subtree? -*/ -bool use_hierarchy; -/* * Should the OOM killer kill all belonging tasks, had it kill one? */
@@ -758,8 +753,6 @@ static inline bool mem_cgroup_is_descendant(struct mem_cgroup *memcg, {if (root == memcg)return true; -if (!root->use_hierarchy) -return false;return cgroup_is_descendant (memcg->css.cgroup, root->css.cgroup); }
kernel/cgroup/cgroup.c +0 -5
@@ -281,9 +281,6 @@ bool cgroup_ssid_enabled(int ssid)* - cpuset: a task can be moved into an empty cpuset, and again it takes * masks of ancestors. * -* - memcg: use_hierarchy is on by default and the cgroup file for the flag -* is not created. -* * - blkcg: blk-throttle becomes properly hierarchical. * * - debug: disallowed on the default hierarchy.
@@ -5156,8 +5153,6 @@ static struct cgroup_subsys_state *css_create(struct cgroup *cgrp, cgroup_parent(parent)) {pr_warn ("%s (%d) created nested cgroup for controller \"%s\" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.\n" , current->comm, current->pid, ss->name); -if (!strcmp (ss->name,"memory" )) -pr_warn ("\"memory\" requires setting use_hierarchy to 1 on the root\n" ); ss->warned_broken_hierarchy = true; }
mm/memcontrol.c +13 -77
156 lines not on this page · raw message
Signature · 1 line
2.26.2
Re: [PATCH v1 1/3] mm: memcg: deprecate the non-hierarchical mode
Quoted 16 lines · Roman Gushchin
The non-hierarchical cgroup v1 mode is a legacy of early days of the memory controller and doesn't bring any value today. However, it complicates the code and creates many edge cases all over the memory controller code.
It's a good time to deprecate it completely.
Functionally this patch enabled is by default for all cgroups and forbids switching it off. Nothing changes if cgroup v2 is used:
hierarchical mode was enforced from scratch.To protect the ABI memory.use_hierarchy interface is preserved with a limited functionality: reading always returns "1", writing of "1" passes silently, writing of any other value fails with
-EINVALand a warning to dmesg (on the first occasion).
Quoted 4 lines
Signed-off-by Roman Gushchin <[email protected]>Acked-by Michal Hocko <[email protected]>Reviewed-by Shakeel Butt <[email protected]>Acked-by David Rientjes <[email protected]>
...and don't let the door hit you on the way out ;-)
PATCH 2/3 docs: cgroup-v1: reflect the deprecation of the non-hierarchical mode
In reply to Roman GushchinUpdate cgroup v1 docs after the deprecation of the non-hierarchical mode of the memory controller.
--- .../admin-guide/cgroup-v1/memcg_test.rst | 8 ++-- .../admin-guide/cgroup-v1/memory.rst | 40 ++++++------------- 2 files changed, 16 insertions(+), 32 deletions(-)
Documentation/admin-guide/cgroup-v1/memcg_test.rst +3 -5
@@ -219,13 +219,11 @@ Under below explanation, we assume CONFIG_MEM_RES_CTRL_SWAP=y. This is an easy way to test page migration, too. -9.5 mkdir/rmdir ---------------- +9.5 nested cgroups +------------------ - When using hierarchy, mkdir/rmdir test should be done. - Use tests like the following:: + Use tests like the following for testing nested cgroups:: - echo 1 >/opt/cgroup/01/memory/use_hierarchy mkdir /opt/cgroup/01/child_a mkdir /opt/cgroup/01/child_b
Documentation/admin-guide/cgroup-v1/memory.rst +13 -27
@@ -77,6 +77,8 @@ Brief summary of control files. memory.soft_limit_in_bytes set/show soft limit of memory usage memory.stat show various statistics memory.use_hierarchy set/show hierarchical account enabled + This knob is deprecated and shouldn't be + used. memory.force_empty trigger forced page reclaim memory.pressure_level set memory pressure notifications memory.swappiness set/show swappiness parameter of vmscan
@@ -495,16 +497,13 @@ cgroup might have some charge associated with it, even though all tasks have migrated away from it. (because we charge against pages, not against tasks.) -We move the stats to root (if use_hierarchy==0) or parent (if -use_hierarchy==1), and no change on the charge except uncharging +We move the stats to parent, and no change on the charge except uncharging from the child. Charges recorded in swap information is not updated at removal of cgroup. Recorded information is discarded and a cgroup which uses swap (swapcache) will be charged as a new owner of it. -About use_hierarchy, see Section 6. - 5. Misc. interfaces ===================
@@ -527,8 +526,6 @@ About use_hierarchy, see Section 6. write will still return success. In this case, it is expected that memory.kmem.usage_in_bytes == memory.usage_in_bytes. - About use_hierarchy, see Section 6. - 5.2 stat file -------------
@@ -675,31 +672,20 @@ hierarchy:: d e In the diagram above, with hierarchical accounting enabled, all memory -usage of e, is accounted to its ancestors up until the root (i.e, c and root), -that has memory.use_hierarchy enabled. If one of the ancestors goes over its -limit, the reclaim algorithm reclaims from the tasks in the ancestor and the -children of the ancestor. - -6.1 Enabling hierarchical accounting and reclaim ------------------------------------------------- - -A memory cgroup by default disables the hierarchy feature. Support -can be enabled by writing 1 to memory.use_hierarchy file of the root cgroup:: +usage of e, is accounted to its ancestors up until the root (i.e, c and root). +If one of the ancestors goes over its limit, the reclaim algorithm reclaims +from the tasks in the ancestor and the children of the ancestor. - # echo 1 > memory.use_hierarchy - -The feature can be disabled by:: +6.1 Hierarchical accounting and reclaim +--------------------------------------- - # echo 0 > memory.use_hierarchy +Hierarchical accounting is enabled by default. Disabling the hierarchical +accounting is deprecated. An attempt to do it will result in a failure +and a warning printed to dmesg. -NOTE1: - Enabling/disabling will fail if either the cgroup already has other - cgroups created below it, or if the parent cgroup has use_hierarchy - enabled. +For compatibility reasons writing 1 to memory.use_hierarchy will always pass:: -NOTE2: - When panic_on_oom is set to "2", the whole system will panic in - case of an OOM event in any cgroup. + # echo 1 > memory.use_hierarchy 7. Soft limits ==============
Signature · 1 line
2.26.2
Re: [PATCH v1 2/3] docs: cgroup-v1: reflect the deprecation of the non-hierarchical mode
Quoted 7 lines · Roman Gushchin
Update cgroup v1 docs after the deprecation of the non-hierarchical mode of the memory controller.
Signed-off-by Roman Gushchin <[email protected]>Reviewed-by Shakeel Butt <[email protected]>Acked-by Michal Hocko <[email protected]>Acked-by David Rientjes <[email protected]>
PATCH 3/3 cgroup: remove obsoleted broken_hierarchy and warned_broken_hierarchy
In reply to Roman GushchinWith the deprecation of the non-hierarchical mode of the memory controller there are no more examples of broken hierarchies left.
Let's remove the cgroup core code which was supposed to print warnings about creating of broken hierarchies.
--- include/linux/cgroup-defs.h | 15 --------------- kernel/cgroup/cgroup.c | 7 ------- 2 files changed, 22 deletions(-)
include/linux/cgroup-defs.h +0 -15
@@ -668,21 +668,6 @@ struct cgroup_subsys {*/ bool threaded:1; -/* -* If %false, this subsystem is properly hierarchical - -* configuration, resource accounting and restriction on a parent -* cgroup cover those of its children. If %true, hierarchy support -* is broken in some ways - some subsystems ignore hierarchy -* completely while others are only implemented half-way. -* -* It's now disallowed to create nested cgroups if the subsystem is -* broken and cgroup core will emit a warning message on such -* cases. Eventually, all subsystems will be made properly -* hierarchical and this will go away. -*/ - bool broken_hierarchy:1; - bool warned_broken_hierarchy:1; -/* the following two fields are initialized automtically during boot */ int id;const char *name;
kernel/cgroup/cgroup.c +0 -7
@@ -5149,13 +5149,6 @@ static struct cgroup_subsys_state *css_create(struct cgroup *cgrp,if (err) goto err_list_del; -if (ss->broken_hierarchy && !ss->warned_broken_hierarchy && -cgroup_parent (parent)) { -pr_warn ("%s (%d) created nested cgroup for controller \"%s\" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.\n" , - current->comm, current->pid, ss->name); - ss->warned_broken_hierarchy = true; - } -return css; err_list_del:
Signature · 1 line
2.26.2
Re: [PATCH v1 3/3] cgroup: remove obsoleted broken_hierarchy and warned_broken_hierarchy
Quoted 9 lines · Roman Gushchin
With the deprecation of the non-hierarchical mode of the memory controller there are no more examples of broken hierarchies left.
Let's remove the cgroup core code which was supposed to print warnings about creating of broken hierarchies.
Signed-off-by Roman Gushchin <[email protected]>Reviewed-by Shakeel Butt <[email protected]>Acked-by David Rientjes <[email protected]>