From 81876c7f655f3686f17e57546263bf50526f7ccd Mon Sep 17 00:00:00 2001 From: Michal Hocko Date: Sat, 17 May 2014 23:19:26 +1000 Subject: [PATCH] memcg-doc-clarify-global-vs-limit-reclaims-fix update doc as per Johannes Signed-off-by: Michal Hocko Cc: Johannes Weiner Cc: KAMEZAWA Hiroyuki Cc: KOSAKI Motohiro Cc: Greg Thelen Cc: Michel Lespinasse Cc: Tejun Heo Cc: Hugh Dickins Cc: Roman Gushchin Signed-off-by: Andrew Morton --- Documentation/cgroups/memory.txt | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt index 5ba92acc0e25..1e5f666b6df2 100644 --- a/Documentation/cgroups/memory.txt +++ b/Documentation/cgroups/memory.txt @@ -241,17 +241,9 @@ global VM. Cgroups can get reclaimed basically under two conditions proportionally wrt. their LRU size in a round robin fashion - when a cgroup or its hierarchical parent (see 6. Hierarchical support) hits hard limit. If the reclaim is unsuccessful, an OOM routine is invoked - to select and kill the bulkiest task in the cgroup. (See 10. OOM Control + to select and kill the bulkiest task in the hiearchy. (See 10. OOM Control below.) -Global and hard-limit reclaims share the same code the only difference -is the objective of the reclaim. The global reclaim aims at balancing -zones' watermarks while the limit reclaim frees some memory to allow new -charges. - -NOTE: Hard limit reclaim does not work for the root cgroup, since we cannot set -any limits on the root cgroup. - Note2: When panic_on_oom is set to "2", the whole system will panic. When oom event notifier is registered, event will be delivered to the root -- 2.39.5