[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110512171725.d367980f.kamezawa.hiroyu@jp.fujitsu.com>
Date: Thu, 12 May 2011 17:17:25 +0900
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ying Han <yinghan@...gle.com>,
Johannes Weiner <jweiner@...hat.com>,
Michal Hocko <mhocko@...e.cz>,
"balbir@...ux.vnet.ibm.com" <balbir@...ux.vnet.ibm.com>,
"nishimura@....nes.nec.co.jp" <nishimura@....nes.nec.co.jp>
Subject: Re: [RFC][PATCH 0/7] memcg async reclaim
On Thu, 12 May 2011 13:22:37 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:
> On Wed, 11 May 2011 20:51:10 -0700
> Andrew Morton <akpm@...ux-foundation.org> wrote:
> Ah, sorry. above was on KVM. without container.
> ==
> [root@...l6-test hilow]# time cp ./tmpfile xxx
>
> real 0m5.197s
> user 0m0.006s
> sys 0m2.599s
> ==
> Hmm, still slow. I'll use real hardware in the next post.
>
I'm now testing on a real machine with some fixes and see
== without async reclaim ==
real 0m6.569s
user 0m0.006s
sys 0m0.976s
== with async reclaim ==
real 0m6.305s
user 0m0.007s
sys 0m0.907s
...in gneral sys time reduced always but 'real' is in error range ;)
yes, no gain.
I'll check what codes in vmscan.c or /mm affects memcg and post a
required fix in step by step. I think I found some..
Thanks,
-Kame
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists