From: Matt Mackall <mpm@selenic.com>
To: Christian Borntraeger <linux-kernel@borntraeger.net>
Cc: linux-kernel@vger.kernel.org, John Bradford <john@grabjohn.com>,
Rik van Riel <riel@redhat.com>,
Lasse K?rkk?inen / Tronic <tronic2@sci.fi>
Subject: Re: Some thoughts about cache and swap
Date: Wed, 9 Jun 2004 13:13:07 -0500 [thread overview]
Message-ID: <20040609181307.GE5414@waste.org> (raw)
In-Reply-To: <200406061038.29470.linux-kernel@borntraeger.net>
On Sun, Jun 06, 2004 at 10:38:25AM +0200, Christian Borntraeger wrote:
> John Bradford wrote:
> > Quote from Rik van Riel <riel@redhat.com>:
> > > I wonder if we should just bite the bullet and implement
> > > LIRS, ARC or CART for Linux. These replacement algorithms
> > > should pretty much detect by themselves which pages are
> > > being used again (within a reasonable time) and which pages
> > > aren't.
> > Is there really much performance to be gained from tuning the 'limited'
> > cache space, or will it just hurt as many or more systems than it helps?
>
> Thats a very good question.
> Most of the time the current algorithm works quite well.
> On the other hand, I definitely know what people mean when they complain
> about cachingand all this stuff. By just copying a big file that I dont use
> afterwards or watching an video I have 2 wonderful scenarios.
Perhaps people should read about the referenced algorithms. LRU
(including the hybrid LRU that Linux uses) is vulnerable to
"scanning" of the sort you're describing, while the above algorithms
have varying degrees of scan-resistance. As lack of scan-resistance
seems to be "the big problem" in the current VM, this looks like an
interesting direction to go in.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2004-06-09 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 14:40 Some thoughts about cache and swap Lasse Kärkkäinen / Tronic
2004-06-05 23:37 ` Rik van Riel
2004-06-06 7:08 ` John Bradford
2004-06-06 8:38 ` Christian Borntraeger
2004-06-09 18:13 ` Matt Mackall [this message]
2004-06-09 19:32 ` John Bradford
2004-06-09 19:32 ` Rik van Riel
2004-06-11 14:07 ` Jörn Engel
2004-06-12 1:50 ` Rik van Riel
2004-06-09 19:45 ` Bill Davidsen
2004-06-09 19:43 ` Bill Davidsen
2004-06-10 7:47 ` Buddy Lumpkin
2004-06-16 14:15 ` jlnance
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=20040609181307.GE5414@waste.org \
--to=mpm@selenic.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@borntraeger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=tronic2@sci.fi \
/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