From: Paul Menage <menage@google.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>,
Balbir Singh <balbir@in.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
nishimura@mxp.nes.nec.co.jp
Cc: 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>,
Li Zefan <lizf@cn.fujitsu.com>,
containers@lists.linux-foundation.org
Subject: Re: memcg: fix fatal livelock in kswapd
Date: Mon, 2 May 2011 15:53:31 -0700 [thread overview]
Message-ID: <BANLkTimhZAdL-HXftE86SyjRrDy9KB+qsg@mail.gmail.com> (raw)
In-Reply-To: <1304366849.15370.27.camel@mulgrave.site>
[ Adding the memcg maintainers ]
On Mon, May 2, 2011 at 1:07 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> 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);
>
>
>
>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-05-02 22:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 20:07 James Bottomley
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
2011-05-07 21:59 ` Balbir Singh
2011-05-07 22:00 ` Balbir Singh
2011-05-02 22:53 ` Paul Menage [this message]
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=BANLkTimhZAdL-HXftE86SyjRrDy9KB+qsg@mail.gmail.com \
--to=menage@google.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=balbir@in.ibm.com \
--cc=chris.mason@oracle.com \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=nishimura@mxp.nes.nec.co.jp \
/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