From: Rik van Riel <riel@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Christoph Lameter <clameter@sgi.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 10:02:14 -0500 [thread overview]
Message-ID: <45B62376.9000303@redhat.com> (raw)
In-Reply-To: <1169540992.6197.202.camel@twins>
Peter Zijlstra wrote:
> 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.
That's fixable. Just bias in favor of the already active
pages and only let pages with a clearly smaller interreference
distance replace them.
> CART might be fixable (my CART-r approach) but I still have to study the
> full ramifications of that (does it hurt other workloads?).
Your CART-r seems reasonable, too.
> Both seems quite capable to distinguish between recency and frequency.
> Neither use this horrid swappiness knob to distinguish between mapped
> and unmapped pages.
Getting rid of swappiness is a very good thing, IMHO.
I have heard about a few customer workloads that required
changes to swappiness in order for the system to be able
to handle their workload at all.
Systems should not have to be tuned like that...
> The main problem I'm having is test cases, notably the lack thereof.
> (and lack of time ofcourse ;-)
Yes, this is always a problem. I am not aware of any complete
test cases to test page replacement.
It would be easy to simulate some database by having part of
the dataset be the index and referencing that in an r^2 way,
and the rest being the data which is referenced less. At that
point you can see how taking frequency into account helps.
However, tests like that are simply not complete. They are
not representative of the things most people do with their
system.
Something like AIM-7 suffers from the same problems...
Anybody?
--
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is. Each group
calls the other unpatriotic.
next prev parent reply other threads:[~2007-01-23 15:10 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
2007-01-23 15:02 ` Rik van Riel [this message]
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=45B62376.9000303@redhat.com \
--to=riel@redhat.com \
--cc=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=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