From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx184.postini.com [74.125.245.184]) by kanga.kvack.org (Postfix) with SMTP id AFB526B0005 for ; Sun, 17 Mar 2013 11:09:39 -0400 (EDT) Date: Sun, 17 Mar 2013 15:09:36 +0000 From: Mel Gorman Subject: Re: [PATCH 03/10] mm: vmscan: Flatten kswapd priority loop Message-ID: <20130317150935.GB2026@suse.de> References: <1363525456-10448-1-git-send-email-mgorman@suse.de> <1363525456-10448-4-git-send-email-mgorman@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Andi Kleen Cc: Linux-MM , Jiri Slaby , Valdis Kletnieks , Rik van Riel , Zlatko Calusic , Johannes Weiner , dormando , Satoru Moriya , Michal Hocko , LKML On Sun, Mar 17, 2013 at 07:36:22AM -0700, Andi Kleen wrote: > Mel Gorman writes: > > > > To avoid infinite looping for high-order allocation requests kswapd will > > not reclaim for high-order allocations when it has reclaimed at least > > twice the number of pages as the allocation request. > > Will this make higher order allocations fail earlier? Or does compaction > still kick in early enough. > Compaction should still kick in early enough. The impact it might have is that direct reclaim/compaction may be used more than it was in the past. -- Mel Gorman SUSE Labs -- 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