From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with ESMTP id 156E49000C2 for ; Tue, 12 Jul 2011 21:15:08 -0400 (EDT) Received: from m4.gw.fujitsu.co.jp (unknown [10.0.50.74]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 086093EE0BD for ; Wed, 13 Jul 2011 10:15:06 +0900 (JST) Received: from smail (m4 [127.0.0.1]) by outgoing.m4.gw.fujitsu.co.jp (Postfix) with ESMTP id A7B4745DE67 for ; Wed, 13 Jul 2011 10:15:05 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (s4.gw.fujitsu.co.jp [10.0.50.94]) by m4.gw.fujitsu.co.jp (Postfix) with ESMTP id 6A0B945DE6B for ; Wed, 13 Jul 2011 10:15:05 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 5D4421DB803F for ; Wed, 13 Jul 2011 10:15:05 +0900 (JST) Received: from ml14.s.css.fujitsu.com (ml14.s.css.fujitsu.com [10.240.81.134]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 21BDC1DB8037 for ; Wed, 13 Jul 2011 10:15:05 +0900 (JST) Message-ID: <4E1CF1A3.3050401@jp.fujitsu.com> Date: Wed, 13 Jul 2011 10:15:15 +0900 From: KOSAKI Motohiro MIME-Version: 1.0 Subject: Re: [PATCH 2/3] mm: page allocator: Initialise ZLC for first zone eligible for zone_reclaim References: <1310389274-13995-1-git-send-email-mgorman@suse.de> <1310389274-13995-3-git-send-email-mgorman@suse.de> In-Reply-To: <1310389274-13995-3-git-send-email-mgorman@suse.de> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: mgorman@suse.de Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org (2011/07/11 22:01), Mel Gorman wrote: > The zonelist cache (ZLC) is used among other things to record if > zone_reclaim() failed for a particular zone recently. The intention > is to avoid a high cost scanning extremely long zonelists or scanning > within the zone uselessly. > > Currently the zonelist cache is setup only after the first zone has > been considered and zone_reclaim() has been called. The objective was > to avoid a costly setup but zone_reclaim is itself quite expensive. If > it is failing regularly such as the first eligible zone having mostly > mapped pages, the cost in scanning and allocation stalls is far higher > than the ZLC initialisation step. > > This patch initialises ZLC before the first eligible zone calls > zone_reclaim(). Once initialised, it is checked whether the zone > failed zone_reclaim recently. If it has, the zone is skipped. As the > first zone is now being checked, additional care has to be taken about > zones marked full. A zone can be marked "full" because it should not > have enough unmapped pages for zone_reclaim but this is excessive as > direct reclaim or kswapd may succeed where zone_reclaim fails. Only > mark zones "full" after zone_reclaim fails if it failed to reclaim > enough pages after scanning. > > Signed-off-by: Mel Gorman If I understand correctly this patch's procs/cons is, pros. 1) faster when zone reclaim doesn't work effectively cons. 2) slower when zone reclaim is off 3) slower when zone recliam works effectively (2) and (3) are frequently happen than (1), correct? At least, I think we need to keep zero impact when zone reclaim mode is off. Thanks. -- 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: email@kvack.org