From: Matt Mackall <mpm@selenic.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Christoph Lameter <clameter@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [RFC] Tracking mlocked pages and moving them off the LRU
Date: Mon, 5 Feb 2007 10:38:47 -0600 [thread overview]
Message-ID: <20070205163847.GI16722@waste.org> (raw)
In-Reply-To: <1170664774.3073.1236.camel@laptopd505.fenrus.org>
On Mon, Feb 05, 2007 at 09:39:34AM +0100, Arjan van de Ven wrote:
> On Sun, 2007-02-04 at 23:57 -0800, Christoph Lameter wrote:
> > Hmmm.. I have had no time to test this one yet but I think this should
> > work. It uses the delayed method and a new page flag PageMlocked() with
> > different semantics. Fix for page migration is also included.
> >
> > Patch avoids to put new anonymous mlocked pages on the LRU. Maybe the same
> > could be done for new pagecache pages?
> >
> > I still need a solution for the problem of not having enough page flag
> > bits on i386 NUMA.
>
> I still don't get why you *really* need such a bit.
There are three possibilities mentioned so far:
1) slow accounting - scan each attached VMA on each mmap/munmap
2) lazy accounting - the same as above, with the work all moved to the
LRU sweep
3) accounting with an extra page flag - still needs to scan VMAs on munmap
Christoph seems to prefer the third.
I wonder if we couldn't stick a rough counter in address_space to
fast-path the slow accounting - we'll typically only have 0 or 1 locks
active.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2007-02-05 16:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 6:20 [RFC] Tracking mlocked pages and moving them off the LRU Christoph Lameter
2007-02-03 8:53 ` Andrew Morton
2007-02-03 17:56 ` Christoph Lameter
2007-02-03 18:04 ` Arjan van de Ven
2007-02-03 18:09 ` Christoph Lameter
2007-02-03 18:55 ` Christoph Lameter
2007-02-03 19:03 ` Christoph Lameter
2007-02-04 1:22 ` Andrew Morton
2007-02-04 1:49 ` Christoph Lameter
2007-02-04 8:16 ` Arjan van de Ven
2007-02-05 6:45 ` Christoph Lameter
2007-02-06 22:05 ` Nate Diller
2007-02-07 8:02 ` Christoph Lameter
2007-02-07 18:39 ` Nate Diller
2007-02-05 7:57 ` Christoph Lameter
2007-02-05 8:39 ` Arjan van de Ven
2007-02-05 16:38 ` Matt Mackall [this message]
2007-02-05 17:34 ` Christoph Lameter
2007-02-05 19:04 ` Christoph Lameter
2007-02-05 17:33 ` Christoph Lameter
2007-02-03 22:58 ` Nigel Cunningham
2007-02-03 10:16 ` Christoph Hellwig
2007-02-03 15:35 ` Martin J. Bligh
2007-02-03 17:59 ` Christoph Lameter
2007-02-03 17:33 ` Christoph Lameter
2007-02-03 22:56 ` Nigel Cunningham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070205163847.GI16722@waste.org \
--to=mpm@selenic.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox