From: Christoph Lameter <clameter@sgi.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/10] split anon and file LRUs
Date: Tue, 6 Nov 2007 18:11:39 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711061808460.5249@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20071103184229.3f20e2f0@bree.surriel.com>
On Sat, 3 Nov 2007, Rik van Riel wrote:
> The current version only has the infrastructure. Large changes to
> the page replacement policy will follow later.
Hmmmm.. I'd rather see where we are going. One other way of addressing
many of these issues is to allow large page sizes on the LRU which will
reduce the number of entities that have to be managed. Both approaches
actually would work in tandem.
> TODO:
> - have any mlocked and ramfs pages live off of the LRU list,
> so we do not need to scan these pages
I think that is the most urgent issue at hand. At least for us.
> - switch to SEQ replacement for the anon LRU lists, so the
> worst case number of pages to scan is reduced greatly.
No idea what that is?
> - figure out if the file LRU lists need page replacement
> changes to help with worst case scenarios
We do not have an accepted standard load. So how would we figure that one
out?
--
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-11-07 2:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 22:42 Rik van Riel
2007-11-03 22:54 ` [RFC PATCH 1/10] move isolate_lru_page to vmscan.c Rik van Riel
2007-11-07 2:13 ` Christoph Lameter
2007-11-03 22:54 ` [RFC PATCH 2/10] free swap space entries if vm_swap_full() Rik van Riel
2007-11-07 2:20 ` Christoph Lameter
2007-11-07 2:48 ` Rik van Riel
2007-11-03 22:55 ` [RFC PATCH 3/10] define page_file_cache Rik van Riel
2007-11-07 2:23 ` Christoph Lameter
2007-11-07 2:55 ` Rik van Riel
2007-11-07 3:02 ` Christoph Lameter
2007-11-07 3:17 ` Rik van Riel
2007-11-07 3:26 ` Christoph Lameter
2007-11-07 14:35 ` Rik van Riel
2007-11-07 18:06 ` Christoph Lameter
2007-11-07 18:17 ` Rik van Riel
2007-11-07 18:18 ` Christoph Lameter
2007-11-03 22:55 ` [RFC PATCH 4/10] debug page_file_cache Rik van Riel
2007-11-03 22:56 ` [RFC PATCH 5/10] use an indexed array for LRU lists and variables Rik van Riel
2007-11-03 23:01 ` [RFC PATCH 6/10] split anon and file LRUs Rik van Riel
2007-11-07 2:28 ` Christoph Lameter
2007-11-07 3:00 ` Rik van Riel
2007-11-03 23:02 ` [RFC PATCH 7/10] clean up the LRU array arithmetic Rik van Riel
2007-11-03 23:03 ` [RFC PATCH 8/10] make split VM and lumpy reclaim work together Rik van Riel
2007-11-03 23:04 ` [RFC PATCH 9/10] split VM and memory controllers Rik van Riel
2007-11-03 23:06 ` [RFC PATCH 10/10] add swapped in pages to the inactive list Rik van Riel
2007-11-07 2:11 ` Christoph Lameter [this message]
2007-11-07 2:23 ` [RFC PATCH 0/10] split anon and file LRUs Rik van Riel
2007-11-07 2:40 ` Christoph Lameter
2007-11-07 2:51 ` Rik van Riel
2007-11-07 17:59 ` Andrew Morton
2007-11-07 18:16 ` 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=Pine.LNX.4.64.0711061808460.5249@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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