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 SMTP id 885E76B004D for ; Thu, 7 May 2009 10:29:12 -0400 (EDT) Received: from localhost (smtp.ultrahosting.com [127.0.0.1]) by smtp.ultrahosting.com (Postfix) with ESMTP id 27A0382C479 for ; Thu, 7 May 2009 10:41:41 -0400 (EDT) Received: from smtp.ultrahosting.com ([74.213.175.254]) by localhost (smtp.ultrahosting.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8QlQcym6mM5 for ; Thu, 7 May 2009 10:41:41 -0400 (EDT) Received: from qirst.com (unknown [74.213.171.31]) by smtp.ultrahosting.com (Postfix) with ESMTP id 2A9D982C48A for ; Thu, 7 May 2009 10:41:36 -0400 (EDT) Date: Thu, 7 May 2009 10:18:47 -0400 (EDT) From: Christoph Lameter Subject: Re: [PATCH -mm] vmscan: make mapped executable pages the first class citizen In-Reply-To: <1241705702.11251.156.camel@twins> Message-ID: References: <20090430072057.GA4663@eskimo.com> <20090430174536.d0f438dd.akpm@linux-foundation.org> <20090430205936.0f8b29fc@riellaptop.surriel.com> <20090430181340.6f07421d.akpm@linux-foundation.org> <20090430215034.4748e615@riellaptop.surriel.com> <20090430195439.e02edc26.akpm@linux-foundation.org> <49FB01C1.6050204@redhat.com> <20090501123541.7983a8ae.akpm@linux-foundation.org> <20090503031539.GC5702@localhost> <1241432635.7620.4732.camel@twins> <20090507121101.GB20934@localhost> <1241705702.11251.156.camel@twins> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org To: Peter Zijlstra Cc: Wu Fengguang , Andrew Morton , Rik van Riel , "linux-kernel@vger.kernel.org" , "tytso@mit.edu" , "linux-mm@kvack.org" , Elladan , Nick Piggin , Johannes Weiner , KOSAKI Motohiro List-ID: On Thu, 7 May 2009, Peter Zijlstra wrote: > It re-instates the young bit for PROT_EXEC pages, so that they will only > be paged when they are really cold, or there is severe pressure. But they are rescanned until then. Really cold means what exactly? I do a back up of a few hundred gigabytes and do not use firefox while the backup is ongoing. Will the firefox pages still be in memory or not? > This simply gives them an edge over regular data. I don't think the > extra scanning is a problem, since you rarely have huge amounts of > executable pages around. > > mlock()'ing all code just doesn't sound like a good alternative. Another possibility may be to put the exec pages on the mlock list and scan the list if under extreme duress? -- 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