From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <464B131F.6090904@yahoo.com.au> Date: Thu, 17 May 2007 00:20:15 +1000 From: Nick Piggin MIME-Version: 1.0 Subject: Re: [PATCH 1/2] Have kswapd keep a minimum order free other than order-0 References: <20070514182456.GA9006@skynet.ie> <1179218576.25205.1.camel@rousalka.dyndns.org> <464AC00E.10704@yahoo.com.au> <464ACA68.2040707@yahoo.com.au> <464AF8DB.9030000@yahoo.com.au> <20070516135039.GA7467@skynet.ie> In-Reply-To: <20070516135039.GA7467@skynet.ie> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Mel Gorman Cc: Nicolas Mailhot , Christoph Lameter , Andy Whitcroft , akpm@linux-foundation.org, Linux Memory Management List List-ID: Mel Gorman wrote: > ====== > > On third thought: The trouble with this solution is that we will now set > the order to that used by the largest kmalloc cache. Bad... this could be > 6 on i386 to 13 if CONFIG_LARGE_ALLOCs is set. The large kmalloc caches are > rarely used and we are used to OOMing if those are utilized to frequently. > > I guess we should only set this for non kmalloc caches then. > So move the call into kmem_cache_create? Would make the min order 3 on > most of my mm machines. > === Also, I might add that the e1000 page allocations failures usually come from kmalloc, so doing this means they might just be protected by chance if someone happens to create a kmem cache of order 3. -- SUSE Labs, Novell Inc. -- 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