From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: balbir@linux.vnet.ibm.com,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [RFC][PATCH 3/4] memcg: softlimit caller via kswapd
Date: Thu, 12 Mar 2009 09:08:39 +0900 [thread overview]
Message-ID: <20090312090839.b77f9560.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090312090311.439B.A69D9226@jp.fujitsu.com>
On Thu, 12 Mar 2009 09:05:43 +0900 (JST)
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> Hi Balbir-san,
>
> > Looks like a dirty hack, replacing sc-> fields this way. I've
> > experimented a lot with per zone balancing and soft limits and it does
> > not work well. The reasons
> >
> > 1. zone watermark balancing has a different goal than soft limit. Soft
> > limits are more of a mem cgroup feature rather than node/zone feature.
> > IIRC, you called reclaim as hot-path for soft limit reclaim, my
> > experimentation is beginning to show changed behaviour
> >
> > On a system with 4 CPUs and 4 Nodes, I find all CPUs spending time
> > doing reclaim, putting the hook in the reclaim path, makes the reclaim
> > dependent on the number of tasks and contention.
> >
> > What does your test data/experimentation show?
>
> you pointed out mainline kernel bug, not kamezawa patch's bug ;-)
> Could you please try following patch?
>
> sorry, this is definitly my fault.
>
>
Thank you!
-Kame
> ---
> mm/vmscan.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index bfd853b..15f7737 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -1470,7 +1470,7 @@ static void shrink_zone(int priority, struct zone *zone,
> int file = is_file_lru(l);
> int scan;
>
> - scan = zone_page_state(zone, NR_LRU_BASE + l);
> + scan = zone_nr_pages(zone, sc, l);
> if (priority) {
> scan >>= priority;
> scan = (scan * percent[file]) / 100;
> --
> 1.6.0.6
>
>
>
>
--
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>
next prev parent reply other threads:[~2009-03-12 0:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 7:37 [RFC][PATCH] memcg: softlimit (Another one) v3 KAMEZAWA Hiroyuki
2009-03-09 7:39 ` [RFC][PATCH 1/4] memcg: add softlimit interface and utilitiy function KAMEZAWA Hiroyuki
2009-03-09 7:44 ` Balbir Singh
2009-03-09 7:55 ` KAMEZAWA Hiroyuki
2009-03-09 8:48 ` Balbir Singh
2009-03-10 5:53 ` KAMEZAWA Hiroyuki
2009-03-10 8:03 ` Balbir Singh
2009-03-10 8:31 ` Balbir Singh
2009-03-09 8:29 ` KAMEZAWA Hiroyuki
2009-03-09 8:54 ` Balbir Singh
2009-03-09 9:07 ` KAMEZAWA Hiroyuki
2009-03-09 7:41 ` [RFC][PATCH 2/4] memcg: softlimit priority and victim scheduler KAMEZAWA Hiroyuki
2009-03-09 7:42 ` [RFC][PATCH 3/4] memcg: softlimit caller via kswapd KAMEZAWA Hiroyuki
2009-03-10 19:02 ` Balbir Singh
2009-03-10 23:52 ` KAMEZAWA Hiroyuki
2009-03-12 0:05 ` KOSAKI Motohiro
2009-03-12 0:08 ` KAMEZAWA Hiroyuki [this message]
2009-03-09 7:43 ` [RFC][PATCH 4/4] memcg: softlimit documenation 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=20090312090839.b77f9560.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--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