From: Craig Kulesa <ckulesa@as.arizona.edu>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] (2/2) reverse mappings for current 2.5.23 VM
Date: Wed, 19 Jun 2002 13:09:23 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.44.0206191248190.4292-100000@loke.as.arizona.edu> (raw)
In-Reply-To: <E17Kiio-0000sO-00@starship>
On Wed, 19 Jun 2002, Daniel Phillips wrote:
> You might conclude from the above that the lru+rmap is superior to
> aging+rmap: while they show the same wall-clock time, lru+rmap consumes
> considerably less disk bandwidth.
I wouldn't draw _any_ conclusions about either patch yet, because as you
said, it's only one type of load. And it was a single tick in vmstat
where page_launder() was aggressive that made the difference between the
two. In a different test, where I had actually *used* more of the
application pages instead of simply closing most of the applications
(save one, the memory hog), the results are likely to have been very
different.
I think that Rik's right: this simply points out that page_launder(), at
least in its interaction with 2.5, needs some tuning. I think both
approaches look very promising, but each for different reasons.
-Craig
--
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/
next parent reply other threads:[~2002-06-19 20:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17Kiio-0000sO-00@starship>
2002-06-19 20:09 ` Craig Kulesa [this message]
2002-06-19 20:44 ` Daniel Phillips
[not found] <Pine.LNX.4.44.0206181340380.3031@loke.as.arizona.edu>
2002-06-19 11:21 ` Craig Kulesa
2002-06-19 11:58 ` Rik van Riel
2002-06-19 17:01 ` Daniel Phillips
2002-06-19 17:18 ` Rik van Riel
2002-06-19 17:46 ` Daniel Phillips
2002-06-19 20:25 ` Craig Kulesa
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.44.0206191248190.4292-100000@loke.as.arizona.edu \
--to=ckulesa@as.arizona.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=phillips@bonn-fries.net \
--cc=riel@conectiva.com.br \
/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