From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrea Arcangeli <andrea@suse.de>, Dave McCracken <dmccr@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 230-objrmap fixes for 2.6.3-mjb2
Date: Wed, 03 Mar 2004 13:39:35 -0800 [thread overview]
Message-ID: <102790000.1078349975@flay> (raw)
In-Reply-To: <20040303185122.GV4922@dualathlon.random>
> what we do in 2.4 and that works pretty well, that is simply to refile
> pages into the active list if they're mlocked, so we don't waste too
> much cpu on them since we don't analyze them too often. this should work
> pretty well for everybody, or peraphs google may prefer to have a fully
> consistent PG_mlocked.
If the page is actually mlocked, wouldn't it make more sense to remove
it from both the active and inactive lists altogether? Scanning it seems
like it'd be less than fruitful.
M.
next prev parent reply other threads:[~2004-03-03 21:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 7:09 230-objrmap fixes for 2.6.3-mjb2 Andrea Arcangeli
2004-03-03 10:58 ` Andrew Morton
2004-03-03 15:46 ` Martin J. Bligh
2004-03-03 15:58 ` Dave McCracken
2004-03-03 16:08 ` Christoph Hellwig
2004-03-03 19:04 ` Mike Kravetz
2004-03-04 15:41 ` Rik van Riel
2004-03-04 15:47 ` Christoph Hellwig
2004-03-04 16:21 ` Rik van Riel
2004-03-04 17:03 ` Matt Mackall
2004-03-03 16:57 ` Andrea Arcangeli
2004-03-03 17:07 ` Dave McCracken
2004-03-03 18:39 ` Andrea Arcangeli
2004-03-03 18:44 ` Dave McCracken
2004-03-03 18:51 ` Andrea Arcangeli
2004-03-03 19:01 ` Dave McCracken
2004-03-03 21:05 ` Andrea Arcangeli
2004-03-03 21:39 ` Martin J. Bligh [this message]
2004-03-03 23:16 ` Andrea Arcangeli
2004-03-03 17:06 ` Andrea Arcangeli
2004-03-03 15:54 ` Martin J. Bligh
2004-03-03 16:14 ` Andrea Arcangeli
2004-03-25 21:45 ` Andrea Arcangeli
2004-03-26 11:57 ` Hugh Dickins
2004-03-26 18:02 ` Andrea Arcangeli
2004-03-26 23:25 ` Andrew Morton
2004-03-27 14:24 ` Andrea Arcangeli
2004-03-27 15:29 ` Dave McCracken
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=102790000.1078349975@flay \
--to=mbligh@aracnet.com \
--cc=andrea@suse.de \
--cc=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.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