From: Johannes Weiner <hannes@cmpxchg.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Greg Thelen <gthelen@google.com>,
Michel Lespinasse <walken@google.com>, Tejun Heo <tj@kernel.org>,
Hugh Dickins <hughd@google.com>,
Roman Gushchin <klamm@yandex-team.ru>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Rik van Riel <riel@redhat.com>
Subject: Re: [PATCH v2 0/4] memcg: Low-limit reclaim
Date: Wed, 28 May 2014 09:49:05 -0400 [thread overview]
Message-ID: <20140528134905.GF2878@cmpxchg.org> (raw)
In-Reply-To: <20140528121023.GA10735@dhcp22.suse.cz>
On Wed, May 28, 2014 at 02:10:23PM +0200, Michal Hocko wrote:
> Hi Andrew, Johannes,
>
> On Mon 28-04-14 14:26:41, Michal Hocko wrote:
> > This patchset introduces such low limit that is functionally similar
> > to a minimum guarantee. Memcgs which are under their lowlimit are not
> > considered eligible for the reclaim (both global and hardlimit) unless
> > all groups under the reclaimed hierarchy are below the low limit when
> > all of them are considered eligible.
> >
> > The previous version of the patchset posted as a RFC
> > (http://marc.info/?l=linux-mm&m=138677140628677&w=2) suggested a
> > hard guarantee without any fallback. More discussions led me to
> > reconsidering the default behavior and come up a more relaxed one. The
> > hard requirement can be added later based on a use case which really
> > requires. It would be controlled by memory.reclaim_flags knob which
> > would specify whether to OOM or fallback (default) when all groups are
> > bellow low limit.
>
> It seems that we are not in a full agreement about the default behavior
> yet. Johannes seems to be more for hard guarantee while I would like to
> see the weaker approach first and move to the stronger model later.
> Johannes, is this absolutely no-go for you? Do you think it is seriously
> handicapping the semantic of the new knob?
Well we certainly can't start OOMing where we previously didn't,
that's called a regression and automatically limits our options.
Any unexpected OOMs will be much more acceptable from a new feature
than from configuration that previously "worked" and then stopped.
> My main motivation for the weaker model is that it is hard to see all
> the corner case right now and once we hit them I would like to see a
> graceful fallback rather than fatal action like OOM killer. Besides that
> the usaceses I am mostly interested in are OK with fallback when the
> alternative would be OOM killer. I also feel that introducing a knob
> with a weaker semantic which can be made stronger later is a sensible
> way to go.
We can't make it stronger, but we can make it weaker. Stronger is the
simpler definition, it's simpler code, your usecases are fine with it,
Greg and I prefer it too. I don't even know what we are arguing about
here.
Patch applies on top of mmots.
---
>From ced6ac70bb274cdaa4c5d78b53420d84fb803dd7 Mon Sep 17 00:00:00 2001
From: Johannes Weiner <hannes@cmpxchg.org>
Date: Wed, 28 May 2014 09:37:05 -0400
Subject: [patch] mm: vmscan: treat memcg low limit as hard guarantee
Don't hide low limit configuration problems behind weak semantics and
quietly breach the set-up guarantees.
Make it simple: memcg guarantees are equivalent to mlocked memory,
anonymous memory without swap, kernel memory, pinned memory etc. -
unreclaimable. If no memory can be reclaimed without otherwise
breaching guarantees, it's a real problem, so let the machine OOM and
dump the memory state in that situation.
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
---
include/linux/memcontrol.h | 5 -----
mm/memcontrol.c | 15 ---------------
mm/vmscan.c | 41 +++++------------------------------------
3 files changed, 5 insertions(+), 56 deletions(-)
diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
index a5cf853129ec..c3a53cbb88eb 100644
--- a/include/linux/memcontrol.h
+++ b/include/linux/memcontrol.h
@@ -94,7 +94,6 @@ bool task_in_mem_cgroup(struct task_struct *task,
extern bool mem_cgroup_within_guarantee(struct mem_cgroup *memcg,
struct mem_cgroup *root);
-extern bool mem_cgroup_all_within_guarantee(struct mem_cgroup *root);
extern struct mem_cgroup *try_get_mem_cgroup_from_page(struct page *page);
extern struct mem_cgroup *mem_cgroup_from_task(struct task_struct *p);
@@ -297,10 +296,6 @@ static inline bool mem_cgroup_within_guarantee(struct mem_cgroup *memcg,
{
return false;
}
-static inline bool mem_cgroup_all_within_guarantee(struct mem_cgroup *root)
-{
- return false;
-}
static inline struct mem_cgroup *try_get_mem_cgroup_from_page(struct page *page)
{
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 4df733e13727..85fdef53fcf1 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -2788,7 +2788,6 @@ static struct mem_cgroup *mem_cgroup_lookup(unsigned short id)
*
* The given group is within its reclaim gurantee if it is below its low limit
* or the same applies for any parent up the hierarchy until root (including).
- * Such a group might be excluded from the reclaim.
*/
bool mem_cgroup_within_guarantee(struct mem_cgroup *memcg,
struct mem_cgroup *root)
@@ -2801,25 +2800,11 @@ bool mem_cgroup_within_guarantee(struct mem_cgroup *memcg,
return true;
if (memcg == root)
break;
-
} while ((memcg = parent_mem_cgroup(memcg)));
return false;
}
-bool mem_cgroup_all_within_guarantee(struct mem_cgroup *root)
-{
- struct mem_cgroup *iter;
-
- for_each_mem_cgroup_tree(iter, root)
- if (!mem_cgroup_within_guarantee(iter, root)) {
- mem_cgroup_iter_break(root, iter);
- return false;
- }
-
- return true;
-}
-
struct mem_cgroup *try_get_mem_cgroup_from_page(struct page *page)
{
struct mem_cgroup *memcg = NULL;
diff --git a/mm/vmscan.c b/mm/vmscan.c
index a8ffe4e616fe..c72493e8fb53 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -2244,20 +2244,14 @@ static inline bool should_continue_reclaim(struct zone *zone,
}
/**
- * __shrink_zone - shrinks a given zone
+ * shrink_zone - shrinks a given zone
*
* @zone: zone to shrink
* @sc: scan control with additional reclaim parameters
- * @honor_memcg_guarantee: do not reclaim memcgs which are within their memory
- * guarantee
- *
- * Returns the number of reclaimed memcgs.
*/
-static unsigned __shrink_zone(struct zone *zone, struct scan_control *sc,
- bool honor_memcg_guarantee)
+static void shrink_zone(struct zone *zone, struct scan_control *sc)
{
unsigned long nr_reclaimed, nr_scanned;
- unsigned nr_scanned_groups = 0;
do {
struct mem_cgroup *root = sc->target_mem_cgroup;
@@ -2274,20 +2268,16 @@ static unsigned __shrink_zone(struct zone *zone, struct scan_control *sc,
do {
struct lruvec *lruvec;
- /* Memcg might be protected from the reclaim */
- if (honor_memcg_guarantee &&
- mem_cgroup_within_guarantee(memcg, root)) {
+ /* Don't reclaim guaranteed memory */
+ if (mem_cgroup_within_guarantee(memcg, root)) {
/*
- * It would be more optimal to skip the memcg
- * subtree now but we do not have a memcg iter
- * helper for that. Anyone?
+ * XXX: skip the entire subtree here
*/
memcg = mem_cgroup_iter(root, memcg, &reclaim);
continue;
}
lruvec = mem_cgroup_zone_lruvec(zone, memcg);
- nr_scanned_groups++;
sc->swappiness = mem_cgroup_swappiness(memcg);
shrink_lruvec(lruvec, sc);
@@ -2316,27 +2306,6 @@ static unsigned __shrink_zone(struct zone *zone, struct scan_control *sc,
} while (should_continue_reclaim(zone, sc->nr_reclaimed - nr_reclaimed,
sc->nr_scanned - nr_scanned, sc));
-
- return nr_scanned_groups;
-}
-
-static void shrink_zone(struct zone *zone, struct scan_control *sc)
-{
- bool honor_guarantee = true;
-
- while (!__shrink_zone(zone, sc, honor_guarantee)) {
- /*
- * The previous round of reclaim didn't find anything to scan
- * because
- * a) the whole reclaimed hierarchy is within guarantee so
- * we fallback to ignore the guarantee because other option
- * would be the OOM
- * b) multiple reclaimers are racing and so the first round
- * should be retried
- */
- if (mem_cgroup_all_within_guarantee(sc->target_mem_cgroup))
- honor_guarantee = false;
- }
}
/* Returns true if compaction should go ahead for a high-order request */
--
1.9.3
next prev parent reply other threads:[~2014-05-28 13:49 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 12:26 [PATCH v2 0/4] memcg: Low-limit reclaim Michal Hocko
2014-04-28 12:26 ` [PATCH 1/4] memcg, mm: introduce lowlimit reclaim Michal Hocko
2014-04-30 22:55 ` Johannes Weiner
2014-05-02 9:36 ` Michal Hocko
2014-05-02 12:07 ` Michal Hocko
2014-05-02 13:01 ` Johannes Weiner
2014-05-02 14:15 ` Michal Hocko
2014-05-02 15:04 ` Johannes Weiner
2014-05-02 15:11 ` Michal Hocko
2014-05-02 15:34 ` Johannes Weiner
2014-05-02 15:48 ` Michal Hocko
2014-05-06 19:58 ` Michal Hocko
2014-05-02 15:58 ` Johannes Weiner
2014-05-02 16:49 ` Michal Hocko
2014-05-02 22:00 ` Johannes Weiner
2014-05-05 14:21 ` Michal Hocko
2014-05-19 16:18 ` Michal Hocko
2014-06-11 15:15 ` Johannes Weiner
2014-06-11 16:08 ` Michal Hocko
[not found] ` <20140506132932.GF19914@cmpxchg.org>
2014-05-06 14:32 ` Michal Hocko
2014-05-06 15:21 ` Johannes Weiner
2014-05-06 16:12 ` Michal Hocko
2014-05-06 16:51 ` Johannes Weiner
2014-05-06 18:30 ` Michal Hocko
2014-05-06 19:55 ` Johannes Weiner
2014-04-28 12:26 ` [PATCH 2/4] memcg: Allow setting low_limit Michal Hocko
2014-04-28 12:26 ` [PATCH 3/4] memcg, doc: clarify global vs. limit reclaims Michal Hocko
2014-04-30 23:03 ` Johannes Weiner
2014-05-02 9:43 ` Michal Hocko
2014-05-06 19:56 ` Michal Hocko
2014-04-28 12:26 ` [PATCH 4/4] memcg: Document memory.low_limit_in_bytes Michal Hocko
2014-04-30 22:57 ` Johannes Weiner
2014-05-02 9:46 ` Michal Hocko
2014-04-28 15:46 ` [PATCH v2 0/4] memcg: Low-limit reclaim Roman Gushchin
2014-04-29 7:42 ` Greg Thelen
2014-04-29 10:50 ` Roman Gushchin
2014-04-29 12:54 ` Michal Hocko
2014-04-30 21:52 ` Andrew Morton
2014-04-30 22:49 ` Johannes Weiner
2014-05-02 12:03 ` Michal Hocko
2014-04-30 21:59 ` Andrew Morton
2014-05-02 11:22 ` Michal Hocko
2014-05-28 12:10 ` Michal Hocko
2014-05-28 13:49 ` Johannes Weiner [this message]
2014-05-28 14:21 ` Michal Hocko
2014-05-28 15:28 ` Johannes Weiner
2014-05-28 15:54 ` Michal Hocko
2014-05-28 16:33 ` Johannes Weiner
2014-06-03 11:07 ` Michal Hocko
2014-06-03 14:22 ` Johannes Weiner
2014-06-04 14:46 ` Michal Hocko
2014-06-04 15:44 ` Johannes Weiner
2014-06-04 19:18 ` Hugh Dickins
2014-06-04 21:45 ` Johannes Weiner
2014-06-05 14:51 ` Michal Hocko
2014-06-05 16:10 ` Johannes Weiner
2014-06-05 16:43 ` Michal Hocko
2014-06-05 18:23 ` Johannes Weiner
2014-06-06 14:44 ` Michal Hocko
2014-06-06 14:46 ` [PATCH 1/2] mm, memcg: allow OOM if no memcg is eligible during direct reclaim Michal Hocko
2014-06-06 14:46 ` [PATCH 2/2] memcg: Allow hard guarantee mode for low limit reclaim Michal Hocko
2014-06-06 15:29 ` Tejun Heo
2014-06-06 15:34 ` Tejun Heo
2014-06-09 8:30 ` Michal Hocko
2014-06-09 13:54 ` Tejun Heo
2014-06-09 22:52 ` Greg Thelen
2014-06-10 16:57 ` Johannes Weiner
2014-06-10 22:16 ` Greg Thelen
2014-06-11 7:57 ` Michal Hocko
2014-06-11 8:00 ` [PATCH 1/2] mm, memcg: allow OOM if no memcg is eligible during direct reclaim Michal Hocko
2014-06-11 8:00 ` [PATCH 2/2] memcg: Allow guarantee reclaim Michal Hocko
2014-06-11 15:36 ` Johannes Weiner
2014-06-12 13:22 ` Michal Hocko
2014-06-12 13:56 ` Johannes Weiner
2014-06-12 14:22 ` Michal Hocko
2014-06-12 16:17 ` Tejun Heo
2014-06-16 12:59 ` Michal Hocko
2014-06-16 13:57 ` Tejun Heo
2014-06-16 14:04 ` Michal Hocko
2014-06-16 14:12 ` Tejun Heo
2014-06-16 14:29 ` Michal Hocko
2014-06-16 14:40 ` Tejun Heo
2014-06-12 16:51 ` Johannes Weiner
2014-06-16 13:22 ` Michal Hocko
2014-06-11 15:20 ` [PATCH 1/2] mm, memcg: allow OOM if no memcg is eligible during direct reclaim Johannes Weiner
2014-06-11 16:14 ` Michal Hocko
2014-06-11 12:31 ` [PATCH 2/2] memcg: Allow hard guarantee mode for low limit reclaim Tejun Heo
2014-06-11 14:11 ` Michal Hocko
2014-06-11 15:34 ` Tejun Heo
2014-06-05 19:36 ` [PATCH v2 0/4] memcg: Low-limit reclaim Tejun Heo
2014-06-05 14:32 ` Michal Hocko
2014-06-05 15:43 ` Johannes Weiner
2014-06-05 16:09 ` Michal Hocko
2014-06-05 16:46 ` Johannes Weiner
2014-05-28 16:17 ` Greg Thelen
2014-06-03 11:09 ` Michal Hocko
[not found] ` <CAHH2K0YuEFdPRVrCfoxYwP5b0GK4cZzL5K3ByubW+087BKcsUg@mail.gmail.com>
2014-06-03 14:44 ` Michal Hocko
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=20140528134905.GF2878@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=gthelen@google.com \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=klamm@yandex-team.ru \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=riel@redhat.com \
--cc=tj@kernel.org \
--cc=walken@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox