From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Andrea Arcangeli <andrea@suse.de>, Andrew Morton <akpm@zip.com.au>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: Bug with shared memory.
Date: Mon, 20 May 2002 09:13:53 -0700 [thread overview]
Message-ID: <1232380940.1021886032@[10.10.2.3]> (raw)
In-Reply-To: <20020520043040.GA21806@dualathlon.random>
> About rmap design I would very much appreciate if Rik could make a
> version of his patch that implements rmap on top of current -aa (it
> wouldn't be a rewrite, just a porting of the strict rmap feature),
> so we can compare apples to apples and benchmark the effect of the
> rmap patch, not the rmap + the hybrid, most of the slowdown during
> paging is most probably due the hybrid, not because of the rmap design,
> the rmap design if something should make things a bit faster during
> swapout infact, by being a bit slower in the more important fast paths.
> It is definitely possible to put a strict rmap on top of -aa without
> the huge "hybrid" thing attached to the rmap code, so without impacting
> at all the rest of the vm. It's just a matter of adding the try_to_unmap
> in shrink_cache and deleting the swap_out call (it's almost as easy as
> shipping a version of Windows without a web browser installed by default).
Is it really the rmap patch, or is this Alan's VM as a whole?
Could you take a look at http://www.surriel.com/patches/ and
see if the rmap 13 patch there is still objectionable to you?
I've been benchmarking rmap 13 against mainline (2.4.19-pre7)
and with the latest lock breakup changes performance now seems
to be about equivalent to mainline (for kernel compile on NUMA-Q).
Those changes reduced system time from 650s to 160s. The only
reason I haven't published results "officially" yet is that I
was sorting out some timer problems with the machine.
M.
next prev parent reply other threads:[~2002-05-20 16:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 15:13 Bug with shared memory Martin Schwidefsky
2002-05-14 19:33 ` Andrew Morton
2002-05-15 22:42 ` Mike Kravetz
2002-05-15 23:07 ` Andrew Morton
2002-05-17 17:53 ` Bill Davidsen
2002-05-17 20:07 ` Mike Kravetz
2002-05-17 20:29 ` Anton Blanchard
2002-05-20 4:30 ` Andrea Arcangeli
2002-05-20 5:21 ` Andrew Morton
2002-05-20 11:34 ` Andrey Savochkin
2002-05-20 14:15 ` Andrea Arcangeli
2002-05-20 19:24 ` Rik van Riel
2002-05-20 23:46 ` Andrea Arcangeli
2002-05-21 0:14 ` Martin J. Bligh
2002-05-21 1:40 ` Andrea Arcangeli
2002-05-20 16:22 ` Martin J. Bligh
2002-05-20 19:38 ` Rik van Riel
2002-05-20 20:06 ` William Lee Irwin III
2002-05-20 16:13 ` Martin J. Bligh [this message]
2002-05-20 16:37 ` Andrea Arcangeli
2002-05-20 17:23 ` Martin J. Bligh
2002-05-20 17:32 ` William Lee Irwin III
2002-05-24 7:33 ` inode highmem imbalance fix [Re: Bug with shared memory.] Andrea Arcangeli
2002-05-24 7:51 ` William Lee Irwin III
2002-05-24 8:04 ` Andrew Morton
2002-05-24 15:20 ` Andrea Arcangeli
2002-05-24 11:47 ` Ed Tomlinson
2002-05-30 11:25 ` Denis Lunev
2002-05-30 17:59 ` Andrea Arcangeli
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='1232380940.1021886032@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=schwidefsky@de.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;
as well as URLs for NNTP newsgroup(s).