[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0702031005510.5461@schroedinger.engr.sgi.com>
Date: Sat, 3 Feb 2007 10:09:56 -0800 (PST)
From: Christoph Lameter <clameter@....com>
To: Arjan van de Ven <arjan@...radead.org>
cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Nick Piggin <nickpiggin@...oo.com.au>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Rik van Riel <riel@...hat.com>
Subject: Re: [RFC] Tracking mlocked pages and moving them off the LRU
On Sat, 3 Feb 2007, Arjan van de Ven wrote:
> it's simpler. You only move them off when you encounter them during a
> scan. No walking early etc etc. Only do work when there is an actual
> situation where you do scan.
Yes but then you do not have an accurate count of MLOCKed pages. We will
only have that count after reclaim has run and removed the pages from the
LRU. That could take some time (or may never happen the way some people
handle memory around here).
> Well.. That's the point! Only IF there is a reclaim scan do you move
> them out again. The fact that these pages are on the list isn't a
> problem. The fact that you keep encountering them over and over again
> during *scanning* is. So Andrews suggestion makes them go away in the
> situations that actually matter
I see... Okay that could be simple to address.
> who cares though.. just do it lazy.
The other issue that the patch should address is to allow the VM to have
statistics that show the actual amount of MLOCKed pages. With the pure
scanner based approach this would no longer work.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists