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 4E4175F0001 for ; Thu, 9 Apr 2009 03:20:02 -0400 (EDT) Date: Thu, 9 Apr 2009 09:22:36 +0200 From: Andi Kleen Subject: Re: [PATCH] [0/16] POISON: Intro Message-ID: <20090409072236.GE14687@one.firstfloor.org> References: <20090407509.382219156@firstfloor.org> <20090407221542.91cd3c42.akpm@linux-foundation.org> <20090408061539.GD17934@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org To: Roland Dreier Cc: Andi Kleen , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org List-ID: On Wed, Apr 08, 2009 at 10:29:34AM -0700, Roland Dreier wrote: > > [1] I didn't consider that one high priority since production > > systems with long uptime shouldn't have much free memory. > > Surely there are windows after a big job exits where lots of memory > might be free. Not sure how big those windows are in practice but it > does seem if a process using 128GB exits then it might take a while > before that memory all gets used again. Yes, it's definitely something to be fixed at some point. Basically just needs a new entry point into the page_alloc buddy allocator to unfree a page. The more tricky part is actually finding a good injector design for testing for it, there's no natural race free way to get a free page. -Andi -- ak@linux.intel.com -- Speaking for myself only. -- 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