From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Hugh Dickins <hugh@veritas.com>
Cc: Ken Chen <kenchen@google.com>, Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org
Subject: Re: [patch] not to disturb page LRU state when unmapping memory range
Date: Wed, 31 Jan 2007 22:43:31 +0100 [thread overview]
Message-ID: <1170279811.10924.32.camel@lappy> (raw)
In-Reply-To: <Pine.LNX.4.64.0701311746230.6135@blonde.wat.veritas.com>
On Wed, 2007-01-31 at 18:02 +0000, Hugh Dickins wrote:
> I'm sympathetic, but I'm going to chicken out on this one. It was
> me who made that set_page_dirty and mark_page_accessed conditional on
> !PageAnon: because I didn't like the waste of time either, and could
> see it was pointless in the PageAnon case. But the situation is much
> less clear to me in the file case, and it is very longstanding code.
> Peter's SetPageReferenced compromise seems appealing: I'd feel better
> about it if we had other raw uses of SetPageReferenced in the balancing
> code, to follow as precedents. There used to be one in do_anonymous_page,
> but Nick and I found that an odd-one-out and conspired to have it removed
> in 2.6.16.
The trouble seems to be that mark_page_accessed() is deformed by this
use once magick. And that really works against us in this case.
The fact is that these pages can have multiple mappings triggering
multiple calls to mark_page_accessed() launching these pages into the
active set. Which clearly seems wrong to me.
I'll go over other callers tomorrow, but I'd really like to change this
to SetPageReferenced(), this will just preserve the PTE young state and
let page reclaim do its usual thing.
Andrew, any strong opinions?
NOTE - the page_mapcount(page) > 1, idea seems interesting but lets not
go there, yet..
NOTE - recall, that in the PG_useonce patches mark_page_accessed() will
again be a simple:
if (!PageReferenced(page))
SetPageReferenced(page);
If only I could come up with a proper set of tests that covers all
this...
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-01-31 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 4:41 [patch] not to disturb page LRU state when unmapping memory range Ken Chen
2007-01-31 12:26 ` Peter Zijlstra
2007-01-31 19:15 ` Balbir Singh
2007-01-31 19:30 ` Christoph Lameter
2007-01-31 18:02 ` Hugh Dickins
2007-01-31 21:43 ` Peter Zijlstra [this message]
2007-01-31 21:51 ` Ken Chen
2007-01-31 22:04 ` Andrew Morton
2007-01-31 22:25 ` Peter Zijlstra
2007-01-31 22:48 ` Andrew Morton
2007-01-31 23:52 ` Peter Zijlstra
2007-02-01 0:33 ` Andrew Morton
2007-02-01 3:21 ` Rik van Riel
2007-02-01 3:13 ` Rik van Riel
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=1170279811.10924.32.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=kenchen@google.com \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).