From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 27 Jan 2007 03:21:33 +0900 From: KAMEZAWA Hiroyuki Subject: Re: [RFC] Track mlock()ed pages Message-Id: <20070127032133.4368e2cb.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <20070126101027.90bf3e63.akpm@osdl.org> References: <45B9A00C.4040701@yahoo.com.au> <20070126031300.59f75b06.akpm@osdl.org> <20070126101027.90bf3e63.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Andrew Morton Cc: clameter@sgi.com, nickpiggin@yahoo.com.au, linux-mm@kvack.org, linux-kernel@vger.kernel.org List-ID: On Fri, 26 Jan 2007 10:10:27 -0800 Andrew Morton wrote: > On Fri, 26 Jan 2007 07:44:42 -0800 (PST) > Christoph Lameter wrote: > > > On Fri, 26 Jan 2007, Andrew Morton wrote: > > > > > > > > Track mlocked pages via a ZVC > > > > > > Why? > > > > Large amounts of mlocked pages may be a problem for > > > > 1. Reclaim behavior. > > > > 2. Defragmentation > > > > We know that. What has that to do with this patch? > 3. just counting mlocked pages.... I have an experience that I was asked by the user to calculate "free" pages on the system where several big 'mlockall' process runs, which shared amounts of pages...when I answered the user cannot trust the result of "/bin/free" if you use mlock processes. It was very fun :P -Kame -- 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