From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 2 Mar 2007 09:38:32 +0100 From: Nick Piggin Subject: Re: The performance and behaviour of the anti-fragmentation related patches Message-ID: <20070302083832.GF5557@wotan.suse.de> References: <20070302054944.GE15867@wotan.suse.de> <20070302060831.GF15867@wotan.suse.de> <20070302062950.GG15867@wotan.suse.de> <20070302071955.GA5557@wotan.suse.de> <20070302081210.GD5557@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: Andrew Morton , Mel Gorman , mingo@elte.hu, jschopp@austin.ibm.com, arjan@infradead.org, torvalds@linux-foundation.org, mbligh@mbligh.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org List-ID: On Fri, Mar 02, 2007 at 12:21:49AM -0800, Christoph Lameter wrote: > On Fri, 2 Mar 2007, Nick Piggin wrote: > > > > If there are billions of pages in the system and we are allocating and > > > deallocating then pages need to be aged. If there are just few pages > > > freeable then we run into issues. > > > > page writeout and vmscan don't work too badly. What are the issues? > > Slow downs up to livelocks with large memory configurations. > > > So what problems that you commonly see now? Some of us here don't > > have 4TB of memory, so you actually have to tell us ;) > > Oh just run a 32GB SMP system with sparsely freeable pages and lots of > allocs and frees and you will see it too. F.e try Linus tree and mlock > a large portion of the memory and then see the fun starting. See also > Rik's list of pathological cases on this. Ah, so your problem is lots of unreclaimable pages. There are heaps of things we can try to reduce the rate at which we scan those. -- 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