From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx164.postini.com [74.125.245.164]) by kanga.kvack.org (Postfix) with SMTP id 6E0C26B0005 for ; Thu, 18 Apr 2013 11:12:04 -0400 (EDT) Date: Thu, 18 Apr 2013 08:11:06 -0700 From: Johannes Weiner Subject: Re: [PATCH 05/10] mm: vmscan: Do not allow kswapd to scan at maximum priority Message-ID: <20130418151106.GG2018@cmpxchg.org> References: <1365710278-6807-1-git-send-email-mgorman@suse.de> <1365710278-6807-6-git-send-email-mgorman@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1365710278-6807-6-git-send-email-mgorman@suse.de> Sender: owner-linux-mm@kvack.org List-ID: To: Mel Gorman Cc: Andrew Morton , Jiri Slaby , Valdis Kletnieks , Rik van Riel , Zlatko Calusic , dormando , Michal Hocko , Kamezawa Hiroyuki , Linux-MM , LKML On Thu, Apr 11, 2013 at 08:57:53PM +0100, Mel Gorman wrote: > Page reclaim at priority 0 will scan the entire LRU as priority 0 is > considered to be a near OOM condition. Kswapd can reach priority 0 quite > easily if it is encountering a large number of pages it cannot reclaim > such as pages under writeback. When this happens, kswapd reclaims very > aggressively even though there may be no real risk of allocation failure > or OOM. > > This patch prevents kswapd reaching priority 0 and trying to reclaim > the world. Direct reclaimers will still reach priority 0 in the event > of an OOM situation. > > Signed-off-by: Mel Gorman > Acked-by: Rik van Riel > Reviewed-by: Michal Hocko Acked-by: Johannes Weiner -- 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: email@kvack.org