From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with SMTP id CED776B004A for ; Tue, 30 Nov 2010 21:59:16 -0500 (EST) Received: from m5.gw.fujitsu.co.jp ([10.0.50.75]) by fgwmail5.fujitsu.co.jp (Fujitsu Gateway) with ESMTP id oB12xEod017905 for (envelope-from kosaki.motohiro@jp.fujitsu.com); Wed, 1 Dec 2010 11:59:14 +0900 Received: from smail (m5 [127.0.0.1]) by outgoing.m5.gw.fujitsu.co.jp (Postfix) with ESMTP id 2993745DE53 for ; Wed, 1 Dec 2010 11:59:14 +0900 (JST) Received: from s5.gw.fujitsu.co.jp (s5.gw.fujitsu.co.jp [10.0.50.95]) by m5.gw.fujitsu.co.jp (Postfix) with ESMTP id 051EE45DE51 for ; Wed, 1 Dec 2010 11:59:14 +0900 (JST) Received: from s5.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s5.gw.fujitsu.co.jp (Postfix) with ESMTP id DE0931DB805D for ; Wed, 1 Dec 2010 11:59:13 +0900 (JST) Received: from m105.s.css.fujitsu.com (m105.s.css.fujitsu.com [10.249.87.105]) by s5.gw.fujitsu.co.jp (Postfix) with ESMTP id 9983A1DB8040 for ; Wed, 1 Dec 2010 11:59:13 +0900 (JST) From: KOSAKI Motohiro Subject: Re: [PATCH 1/3] mm: kswapd: Stop high-order balancing when any suitable zone is balanced In-Reply-To: <1291171667.12777.51.camel@sli10-conroe> References: <20101201112354.ABA8.A69D9226@jp.fujitsu.com> <1291171667.12777.51.camel@sli10-conroe> Message-Id: <20101201115401.ABB1.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Date: Wed, 1 Dec 2010 11:59:12 +0900 (JST) Sender: owner-linux-mm@kvack.org To: Shaohua Li Cc: kosaki.motohiro@jp.fujitsu.com, Mel Gorman , Simon Kirby , Dave Hansen , linux-mm , linux-kernel List-ID: > On Wed, 2010-12-01 at 10:23 +0800, KOSAKI Motohiro wrote: > > > On Wed, 2010-12-01 at 01:15 +0800, Mel Gorman wrote: > > > > When the allocator enters its slow path, kswapd is woken up to balance the > > > > node. It continues working until all zones within the node are balanced. For > > > > order-0 allocations, this makes perfect sense but for higher orders it can > > > > have unintended side-effects. If the zone sizes are imbalanced, kswapd > > > > may reclaim heavily on a smaller zone discarding an excessive number of > > > > pages. The user-visible behaviour is that kswapd is awake and reclaiming > > > > even though plenty of pages are free from a suitable zone. > > > > > > > > This patch alters the "balance" logic to stop kswapd if any suitable zone > > > > becomes balanced to reduce the number of pages it reclaims from other zones. > > > from my understanding, the patch will break reclaim high zone if a low > > > zone meets the high order allocation, even the high zone doesn't meet > > > the high order allocation. This, for example, will make a high order > > > allocation from a high zone fallback to low zone and quickly exhaust low > > > zone, for example DMA. This will break some drivers. > > > > Have you seen patch [3/3]? I think it migigate your pointed issue. > yes, it improves a lot, but still possible for small systems. Ok, I got you. so please define your "small systems" word? we can't make perfect VM heuristics obviously, then we need to compare pros/cons. Of cource, I'm glad if you have better idea and show it. -- 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 policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org