From: Christoph Lameter <clameter@engr.sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-mm@kvack.org, sjiang@lanl.gov, rni@andrew.cmu.edu,
a.p.zijlstra@chello.nl, riel@redhat.com
Subject: Re: Benchmarks to exploit LRU deficiencies
Date: Tue, 11 Oct 2005 08:23:32 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0510110820070.897@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200510110213.29937.ak@suse.de>
On Tue, 11 Oct 2005, Andi Kleen wrote:
> I think if you want to really see advantages you should not implement
> the advanced algorithms for the page cache, but for the inode/dentry
> cache. We seem to have far more problems in this area than with the
> standard page cache.
We have had significant problems with the page cache for a long time.
Systems slow down because node memory is filled up with page cache
pages that are not properly reclaimed and thus off node allocation
occurs. The current method of freeing memory requires a scan which
makes this whole thing painfully slow. There are special hacks in SLES9 to
deal with these issues.
Moreover the LRU algorithm leads to the eviction of important pages if a
program does a simple scan of a large file.
I hope that the advanced page replacement methods address some of these
problems.
--
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:[~2005-10-11 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 18:46 Marcelo Tosatti
2005-10-11 0:13 ` Andi Kleen
2005-10-10 20:26 ` Marcelo Tosatti
2005-10-11 0:41 ` Andi Kleen
2005-10-10 23:21 ` Marcelo Tosatti
2005-10-11 8:10 ` Andi Kleen
2005-10-11 1:04 ` Rik van Riel
2005-10-11 15:23 ` Christoph Lameter [this message]
2005-10-13 8:00 ` Magnus Damm
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.62.0510110820070.897@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@suse.de \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=riel@redhat.com \
--cc=rni@andrew.cmu.edu \
--cc=sjiang@lanl.gov \
/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