From: Rik van Riel <riel@conectiva.com.br>
To: Dave Jones <davej@suse.de>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
Craig Kulesa <ckulesa@as.arizona.edu>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Linus Torvalds <torvalds@transmeta.com>,
rwhron@earthlink.net
Subject: Re: [PATCH] (1/2) reverse mapping VM for 2.5.23 (rmap-13b)
Date: Wed, 19 Jun 2002 14:35:45 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.44L.0206191429300.2598-100000@imladris.surriel.com> (raw)
In-Reply-To: <20020619191136.H29373@suse.de>
On Wed, 19 Jun 2002, Dave Jones wrote:
> On Wed, Jun 19, 2002 at 07:00:57PM +0200, Daniel Phillips wrote:
> > > ...Hope this is of use to someone! It's certainly been a fun and
> > > instructive exercise for me so far. ;)
> > It's intensely useful. It changes the whole character of the VM discussion
> > at the upcoming kernel summit from 'should we port rmap to mainline?' to 'how
> > well does it work' and 'what problems need fixing'. Much more useful.
>
> Absolutely. Maybe Randy Hron (added to Cc) can find some spare time
> to benchmark these sometime before the summit too[1]. It'll be very
> interesting to see where it fits in with the other benchmark results
> he's collected on varying workloads.
Note that either version is still untuned and rmap for 2.5
still needs pte-highmem support.
I am encouraged by Craig's test results, which show that
rmap did a LOT less swapin IO and rmap with page aging even
less. The fact that it did too much swapout IO means one
part of the system needs tuning but doesn't say much about
the thing as a whole.
In fact, I have a feeling that our tools are still too
crude, we really need/want some statistics of what's
happening inside the VM ... I'll work on those shortly.
Once we do have the tools to look at what's happening
inside the VM we should be much better able to tune the
right places inside the VM.
regards,
Rik
--
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/ http://distro.conectiva.com/
--
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 prev parent reply other threads:[~2002-06-19 17:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 11:18 Craig Kulesa
2002-06-19 16:18 ` Andrew Morton
2002-06-19 17:00 ` Daniel Phillips
2002-06-19 17:11 ` Dave Jones
2002-06-19 17:35 ` Rik van Riel [this message]
2002-06-19 19:53 ` Ingo Molnar
2002-06-19 20:21 ` Craig Kulesa
2002-06-19 20:24 ` Linus Torvalds
2002-06-20 12:25 ` VM benchmarks for 2.5 (mainline & rmap patches) Craig Kulesa
2002-06-24 21:34 ` [PATCH] (1/2) reverse mapping VM for 2.5.23 (rmap-13b) Martin J. Bligh
2002-06-24 21:39 ` Rik van Riel
2002-06-24 21:56 ` Martin J. Bligh
2002-07-04 5:19 ` Daniel Phillips
2002-06-24 15:02 ` Rik van Riel
2002-06-19 19:04 ` Steven Cole
2002-06-19 22:44 ` William Lee Irwin III
2002-06-20 12:08 ` [PATCH] Updated rmap VM for 2.5.23 (SMP, preempt fixes) Craig Kulesa
2002-06-20 12:45 ` 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.44L.0206191429300.2598-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--cc=ckulesa@as.arizona.edu \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=phillips@bonn-fries.net \
--cc=rwhron@earthlink.net \
--cc=torvalds@transmeta.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