From: Rik van Riel <riel@redhat.com>
To: balbir@in.ibm.com
Cc: Christoph Lameter <clameter@sgi.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Subject: Re: [PATCH] Take anonymous pages off the LRU if we have no swap
Date: Thu, 22 Feb 2007 12:04:56 -0500 [thread overview]
Message-ID: <45DDCD38.6000807@redhat.com> (raw)
In-Reply-To: <45DDB85D.209@in.ibm.com>
Balbir Singh wrote:
> Rik van Riel wrote:
>> Christoph Lameter wrote:
>>> On Wed, 21 Feb 2007, Rik van Riel wrote:
>>>
>> Absolutely. I am convinced that the whole "swappiness" thing
>> of scanning past the anonymous pages in order to find the page
>> cache pages will fall apart on 256GB systems even with somewhat
>> friendly workloads.
>
> That should probably make a good case for splitting the LRU
> into unmapped and mapped page LRU's :-)
Please read http://linux-mm.org/PageReplacementDesign.
There are good reasons why the split should probably be
between anonymous/swap backed and file backed pages,
not between mapped and unmapped.
> I hope to get to it, implement it and get some results.
Ditto here :)
--
All Rights Reversed
--
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-02-22 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 22:12 Christoph Lameter
2007-02-21 23:17 ` Rik van Riel
2007-02-22 0:06 ` Christoph Lameter
2007-02-22 2:17 ` Rik van Riel
2007-02-22 3:09 ` Christoph Lameter
2007-02-22 12:13 ` Rik van Riel
2007-02-22 15:35 ` Balbir Singh
2007-02-22 17:04 ` Rik van Riel [this message]
2007-02-22 17:21 ` Paul Menage
2007-02-22 18:45 ` Christoph Lameter
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=45DDCD38.6000807@redhat.com \
--to=riel@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=svaidy@linux.vnet.ibm.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