From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 19 Jul 2006 00:59:53 +0900 From: KAMEZAWA Hiroyuki Subject: Re: [PATCH] mm: inactive-clean list Message-Id: <20060719005953.5e34f4f1.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: References: <1153167857.31891.78.camel@lappy> <1153224998.2041.15.camel@lappy> <44BCE86A.4030602@mbligh.org> <20060718072545.7cfed5b2.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: Christoph Lameter Cc: akpm@osdl.org, mbligh@mbligh.org, a.p.zijlstra@chello.nl, linux-mm@kvack.org, torvalds@osdl.org, linux-kernel@vger.kernel.org List-ID: On Tue, 18 Jul 2006 07:45:21 -0700 (PDT) Christoph Lameter wrote: > On Tue, 18 Jul 2006, Andrew Morton wrote: > > > Christoph Lameter wrote: > > > What other types of non freeable pages could exist? > > > > PageWriteback() pages (potentially all of memory) > > Doesnt write throttling take care of that? > > > Pinned pages (various transient conditions, mainly get_user_pages()) > > Hmm.... > > > Some pages whose buffers are attached to an ext3 journal. > > These are just pinned by an increased refcount right? > > > Possibly NFS unstable pages. > > These are tracked by NR_NFS_UNSTABLE. > > Maybe we need a NR_UNSTABLE that includes pinned pages? > I'm not sure what was discussed in VM summit. If I miss the point, sorry. I think the important thing here is the amount of free pages we try to keep. Remaining unused pages as page cache(and not free them) may help performance if lucky but increases uncertainity. Now, enlarging min_free_kbytes or mempool is useful to avoid page allocation failure in device drivers, which does write-back of dirty pages. I think controlling free memory itself is better than controlling *used* inactive clean pages. Bye -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