From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: lse-tech <lse-tech@lists.sourceforge.net>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: Performance of partial object-based rmap
Date: Thu, 20 Feb 2003 17:44:17 -0800 [thread overview]
Message-ID: <278890000.1045791857@flay> (raw)
In-Reply-To: <7490000.1045715152@[10.10.2.4]>
> The performance delta between 2.5.62-mjb1 and 2.5.62-mjb2 is caused
> by the partial object-based rmap patch (written by Dave McCracken).
> I expect this patch to have an increasing impact on workloads with
> more processes, and it should give a substantial space saving as
> well as a performance increase. Results from 16x NUMA-Q system ...
>
> Profile comparison:
>
> before
> 15525 page_remove_rmap
> 6415 page_add_rmap
>
> after
> 2055 page_add_rmap
> 1983 page_remove_rmap
Did some space consumption comparisons on make -j 256:
before:
24116 pte_chain objects in slab cache
after:
716 pte_chain objects in slab cache
The vast majority of anonymous pages (for which we're using the non
object based method) are singletons, and hence use pte_direct ...
hence the massive space reduction.
M.
next prev parent reply other threads:[~2003-02-21 1:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 4:25 Performance of partial object-based rmap Martin J. Bligh
2003-02-20 4:47 ` William Lee Irwin III
2003-02-20 5:14 ` Martin J. Bligh
2003-02-20 5:16 ` [Lse-tech] " William Lee Irwin III
2003-02-20 5:27 ` Martin J. Bligh
2003-02-21 1:44 ` Martin J. Bligh [this message]
2003-02-21 3:08 ` Andrew Morton
2003-02-21 3:25 ` Rik van Riel
2003-02-21 3:47 ` Andrew Morton
2003-02-21 4:25 ` Rik van Riel
2003-02-21 10:00 ` William Lee Irwin III
2003-02-21 19:15 ` [Lse-tech] " William Lee Irwin III
2003-02-21 19:27 ` William Lee Irwin III
2003-02-21 3:32 ` Martin J. Bligh
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=278890000.1045791857@flay \
--to=mbligh@aracnet.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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