From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christoph Lameter <clameter@sgi.com>
Cc: Rik van Riel <riel@redhat.com>, Balbir Singh <balbir@in.ibm.com>,
Andrea Arcangeli <andrea@suse.de>,
Niki Hammler <mailinglists@nobaq.net>,
linux-kernel@vger.kernel.org,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Subject: Re: Why active list and inactive list?
Date: Tue, 23 Jan 2007 09:29:52 +0100 [thread overview]
Message-ID: <1169540992.6197.202.camel@twins> (raw)
In-Reply-To: <Pine.LNX.4.64.0701221801420.30595@schroedinger.engr.sgi.com>
On Mon, 2007-01-22 at 18:03 -0800, Christoph Lameter wrote:
> What happened to all those advanced page replacement endeavors?
They are here:
http://programming.kicks-ass.net/kernel-patches/page-replace/2.6.19-pr1/
I should update to .20 soonish.
> What is the most promising of those?
I'm still torn between CLOCK-Pro and CART.
CLOCK-Pro is still vulnerable to the cyclic scan use case, since at that
time all pages will have equal distance.
CART might be fixable (my CART-r approach) but I still have to study the
full ramifications of that (does it hurt other workloads?).
Both seems quite capable to distinguish between recency and frequency.
Neither use this horrid swappiness knob to distinguish between mapped
and unmapped pages.
The main problem I'm having is test cases, notably the lack thereof.
(and lack of time ofcourse ;-)
next prev parent reply other threads:[~2007-01-23 8:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 0:10 Why active list and inactive list? Niki Hammler
2007-01-23 0:39 ` Andrea Arcangeli
2007-01-23 1:31 ` Balbir Singh
2007-01-23 1:40 ` Christoph Lameter
2007-01-23 1:49 ` Rik van Riel
2007-01-23 2:03 ` Christoph Lameter
2007-01-23 2:17 ` Rik van Riel
2007-01-23 2:44 ` Christoph Lameter
2007-01-23 2:50 ` Rik van Riel
2007-01-23 8:29 ` Peter Zijlstra [this message]
2007-01-23 15:02 ` Rik van Riel
2007-01-30 11:01 ` Howard Chu
2007-01-23 3:36 ` Balbir Singh
2007-01-23 3:43 ` Christoph Lameter
2007-01-23 3:51 ` Balbir Singh
2007-01-23 3:18 ` Balbir Singh
2007-01-23 3:28 ` Christoph Lameter
2007-01-23 3:45 ` Balbir Singh
2007-01-23 3:51 ` Christoph Lameter
2007-01-23 1:42 ` Rik van Riel
2007-01-23 2:13 ` Andrea Arcangeli
2007-01-23 4:17 ` Nick Piggin
2007-01-23 4:34 ` Rik van Riel
2007-01-23 5:51 ` Balbir Singh
2007-01-23 4:46 ` Balbir Singh
[not found] <7Gpmk-5fN-21@gated-at.bofh.it>
2007-01-30 10:23 ` Howard Chu
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=1169540992.6197.202.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=andrea@suse.de \
--cc=balbir@in.ibm.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mailinglists@nobaq.net \
--cc=riel@redhat.com \
--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