From: Johannes Weiner <hannes@cmpxchg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>, Tejun Heo <tj@kernel.org>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] mm: memcontrol: remove hierarchy restrictions for swappiness and oom_control
Date: Thu, 17 Apr 2014 08:56:57 -0400 [thread overview]
Message-ID: <20140417125657.GA23470@cmpxchg.org> (raw)
In-Reply-To: <20140416143425.c2b6f511cf4c6cd7336134b3@linux-foundation.org>
On Wed, Apr 16, 2014 at 02:34:25PM -0700, Andrew Morton wrote:
> On Wed, 16 Apr 2014 17:13:18 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:
>
> > Per-memcg swappiness and oom killing can currently not be tweaked on a
> > memcg that is part of a hierarchy, but not the root of that hierarchy.
> > Users have complained that they can't configure this when they turned
> > on hierarchy mode. In fact, with hierarchy mode becoming the default,
> > this restriction disables the tunables entirely.
> >
> > But there is no good reason for this restriction. The settings for
> > swappiness and OOM killing are taken from whatever memcg whose limit
> > triggered reclaim and OOM invocation, regardless of its position in
> > the hierarchy tree.
> >
> > Allow setting swappiness on any group. The knob on the root memcg
> > already reads the global VM swappiness, make it writable as well.
> >
> > Allow disabling the OOM killer on any non-root memcg.
>
> Documentation/cgroups/memory.txt needs updates?
Yes, that makes sense, thanks. How about this?
---
Subject: [patch] mm: memcontrol: remove hierarchy restrictions for swappiness and oom_control fix
Update Documentation/cgroups/memory.txt
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
---
diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
index 2622115276aa..1829c65f8371 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -535,17 +535,15 @@ Note:
5.3 swappiness
-Similar to /proc/sys/vm/swappiness, but affecting a hierarchy of groups only.
+Similar to /proc/sys/vm/swappiness, but only affecting reclaim that is
+triggered by this cgroup's hard limit. The tunable in the root cgroup
+corresponds to the global swappiness setting.
+
Please note that unlike the global swappiness, memcg knob set to 0
really prevents from any swapping even if there is a swap storage
available. This might lead to memcg OOM killer if there are no file
pages to reclaim.
-Following cgroups' swappiness can't be changed.
-- root cgroup (uses /proc/sys/vm/swappiness).
-- a cgroup which uses hierarchy and it has other cgroup(s) below it.
-- a cgroup which uses hierarchy and not the root of hierarchy.
-
5.4 failcnt
A memory cgroup provides memory.failcnt and memory.memsw.failcnt files.
@@ -754,7 +752,6 @@ You can disable the OOM-killer by writing "1" to memory.oom_control file, as:
#echo 1 > memory.oom_control
-This operation is only allowed to the top cgroup of a sub-hierarchy.
If OOM-killer is disabled, tasks under cgroup will hang/sleep
in memory cgroup's OOM-waitqueue when they request accountable memory.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Weiner <hannes@cmpxchg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>, Tejun Heo <tj@kernel.org>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch] mm: memcontrol: remove hierarchy restrictions for swappiness and oom_control
Date: Thu, 17 Apr 2014 08:56:57 -0400 [thread overview]
Message-ID: <20140417125657.GA23470@cmpxchg.org> (raw)
In-Reply-To: <20140416143425.c2b6f511cf4c6cd7336134b3@linux-foundation.org>
On Wed, Apr 16, 2014 at 02:34:25PM -0700, Andrew Morton wrote:
> On Wed, 16 Apr 2014 17:13:18 -0400 Johannes Weiner <hannes@cmpxchg.org> wrote:
>
> > Per-memcg swappiness and oom killing can currently not be tweaked on a
> > memcg that is part of a hierarchy, but not the root of that hierarchy.
> > Users have complained that they can't configure this when they turned
> > on hierarchy mode. In fact, with hierarchy mode becoming the default,
> > this restriction disables the tunables entirely.
> >
> > But there is no good reason for this restriction. The settings for
> > swappiness and OOM killing are taken from whatever memcg whose limit
> > triggered reclaim and OOM invocation, regardless of its position in
> > the hierarchy tree.
> >
> > Allow setting swappiness on any group. The knob on the root memcg
> > already reads the global VM swappiness, make it writable as well.
> >
> > Allow disabling the OOM killer on any non-root memcg.
>
> Documentation/cgroups/memory.txt needs updates?
Yes, that makes sense, thanks. How about this?
---
Subject: [patch] mm: memcontrol: remove hierarchy restrictions for swappiness and oom_control fix
Update Documentation/cgroups/memory.txt
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
---
diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
index 2622115276aa..1829c65f8371 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -535,17 +535,15 @@ Note:
5.3 swappiness
-Similar to /proc/sys/vm/swappiness, but affecting a hierarchy of groups only.
+Similar to /proc/sys/vm/swappiness, but only affecting reclaim that is
+triggered by this cgroup's hard limit. The tunable in the root cgroup
+corresponds to the global swappiness setting.
+
Please note that unlike the global swappiness, memcg knob set to 0
really prevents from any swapping even if there is a swap storage
available. This might lead to memcg OOM killer if there are no file
pages to reclaim.
-Following cgroups' swappiness can't be changed.
-- root cgroup (uses /proc/sys/vm/swappiness).
-- a cgroup which uses hierarchy and it has other cgroup(s) below it.
-- a cgroup which uses hierarchy and not the root of hierarchy.
-
5.4 failcnt
A memory cgroup provides memory.failcnt and memory.memsw.failcnt files.
@@ -754,7 +752,6 @@ You can disable the OOM-killer by writing "1" to memory.oom_control file, as:
#echo 1 > memory.oom_control
-This operation is only allowed to the top cgroup of a sub-hierarchy.
If OOM-killer is disabled, tasks under cgroup will hang/sleep
in memory cgroup's OOM-waitqueue when they request accountable memory.
next prev parent reply other threads:[~2014-04-17 12:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 21:13 [patch] mm: memcontrol: remove hierarchy restrictions for swappiness and oom_control Johannes Weiner
2014-04-16 21:13 ` Johannes Weiner
2014-04-16 21:13 ` Johannes Weiner
[not found] ` <1397682798-22906-1-git-send-email-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2014-04-16 21:34 ` Andrew Morton
2014-04-16 21:34 ` Andrew Morton
2014-04-16 21:34 ` Andrew Morton
2014-04-17 12:56 ` Johannes Weiner [this message]
2014-04-17 12:56 ` Johannes Weiner
2014-04-18 11:36 ` Michal Hocko
2014-04-18 11:36 ` Michal Hocko
2014-04-24 12:19 ` Johannes Weiner
2014-04-24 12:19 ` Johannes Weiner
2014-04-24 14:27 ` [RFC PATCH] vmscan: memcg: Always use swappiness of the reclaimed memcg " Michal Hocko
2014-04-24 14:27 ` Michal Hocko
2014-04-24 14:27 ` Michal Hocko
[not found] ` <20140424142704.GC7644-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2014-04-30 9:09 ` Michal Hocko
2014-04-30 9:09 ` Michal Hocko
2014-04-30 9:09 ` Michal Hocko
2014-04-30 23:06 ` Johannes Weiner
2014-04-30 23:06 ` Johannes Weiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140417125657.GA23470@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.