From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
Ying Han <yinghan@google.com>,
Johannes Weiner <jweiner@redhat.com>,
Michal Hocko <mhocko@suse.cz>
Subject: Re: [PATCH][BUGFIX] memcg fix zone congestion
Date: Fri, 13 May 2011 15:24:26 +0900 [thread overview]
Message-ID: <20110513152426.cbb91a84.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20110513131514.a7ec1328.nishimura@mxp.nes.nec.co.jp>
On Fri, 13 May 2011 13:15:14 +0900
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> On Fri, 13 May 2011 12:10:30 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> >
> > ZONE_CONGESTED should be a state of global memory reclaim.
> > If not, a busy memcg sets this and give unnecessary throttoling in
> > wait_iff_congested() against memory recalim in other contexts. This makes
> > system performance bad.
> >
> hmm, nice catch.
>
> Just from my curiosity, is there any number of performance improvement by this patch?
>
I guess impact of this patch is very limited. (And I've tested but cannot measure
the score. I need some special application/settings.)
I think, with small memcg, we'll see nr_dirty==nr_congested situaion often and
set ZONE_CONGESTED. But the effect of patch can be seen in the another place.
To see the effect of patch, the system need to reclaim memory eagerly with memory
shortage. In that situation, everything is slow. This patch just removes a extra
burden which is put on by mistake.
Thanks,
-Kame
--
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>
next prev parent reply other threads:[~2011-05-13 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 3:10 KAMEZAWA Hiroyuki
2011-05-13 3:53 ` Minchan Kim
2011-05-13 4:15 ` Daisuke Nishimura
2011-05-13 6:24 ` KAMEZAWA Hiroyuki [this message]
2011-05-13 5:25 ` Ying Han
2011-05-13 6:25 ` KAMEZAWA Hiroyuki
2011-05-13 6:25 ` Andrew Morton
2011-05-13 6:52 ` KAMEZAWA Hiroyuki
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=20110513152426.cbb91a84.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=jweiner@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=yinghan@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