From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Chris Mason <chris.mason@oracle.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
containers@lists.linux-foundation.org
Subject: memcg: fix fatal livelock in kswapd
Date: Mon, 02 May 2011 15:07:29 -0500 [thread overview]
Message-ID: <1304366849.15370.27.camel@mulgrave.site> (raw)
The fatal livelock in kswapd, reported in this thread:
http://marc.info/?t=130392066000001
Is mitigateable if we prevent the cgroups code being so aggressive in
its zone shrinking (by reducing it's default shrink from 0 [everything]
to DEF_PRIORITY [some things]). This will have an obvious knock on
effect to cgroup accounting, but it's better than hanging systems.
Signed-off-by: James Bottomley <James.Bottomley@suse.de>
---
>From 74b62fc417f07e1411d98181631e4e097c8e3e68 Mon Sep 17 00:00:00 2001
From: James Bottomley <James.Bottomley@HansenPartnership.com>
Date: Mon, 2 May 2011 14:56:29 -0500
Subject: [PATCH] vmscan: move containers scan back to default priority
diff --git a/mm/vmscan.c b/mm/vmscan.c
index f6b435c..46cde92 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -2173,8 +2173,12 @@ unsigned long mem_cgroup_shrink_node_zone(struct mem_cgroup *mem,
* if we don't reclaim here, the shrink_zone from balance_pgdat
* will pick up pages from other mem cgroup's as well. We hack
* the priority and make it zero.
+ *
+ * FIXME: jejb: zero here was causing a livelock in the
+ * shrinker so changed to DEF_PRIORITY to fix this. Now need to
+ * sort out cgroup accounting.
*/
- shrink_zone(0, zone, &sc);
+ shrink_zone(DEF_PRIORITY, zone, &sc);
trace_mm_vmscan_memcg_softlimit_reclaim_end(sc.nr_reclaimed);
next reply other threads:[~2011-05-02 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 20:07 James Bottomley [this message]
2011-05-02 22:48 ` Johannes Weiner
2011-05-02 23:14 ` Ying Han
2011-05-02 23:58 ` James Bottomley
2011-05-03 6:38 ` Johannes Weiner
2011-05-03 14:11 ` James Bottomley
2011-05-05 21:00 ` Andrew Morton
2011-05-03 6:11 ` Johannes Weiner
[not found] ` <BANLkTikKhjmPJKHiJa2hRBdUF2=oe8HZzg@mail.gmail.com>
2011-05-07 22:00 ` Balbir Singh
2011-05-02 22:53 ` Paul Menage
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=1304366849.15370.27.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=chris.mason@oracle.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@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
all inboxes | Powered by JetHome®