From: Nai Xia <nai.xia@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Andi Kleen <andi@firstfloor.org>,
Christoph Lameter <cl@linux-foundation.org>,
Elladan <elladan@eskimo.com>, Nick Piggin <npiggin@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Peter Zijlstra <peterz@infradead.org>,
Rik van Riel <riel@redhat.com>, "tytso@mit.edu" <tytso@mit.edu>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"minchan.kim@gmail.com" <minchan.kim@gmail.com>
Subject: Re: [PATCH 0/3] make mapped executable pages the first class citizen (with test cases)
Date: Fri, 10 Jul 2009 15:24:29 +0800 [thread overview]
Message-ID: <ab418ea90907100024xe95ab44pb0809d262e616565@mail.gmail.com> (raw)
In-Reply-To: <20090608091044.880249722@intel.com>
Hi,
I was able to launch some tests with SPEC cpu2006.
The benchmark was based on mmotm
commit 0b7292956dbdfb212abf6e3c9cfb41e9471e1081 on a intel Q6600 box with
4G ram. The kernel cmdline mem=500M was used to see how good exec-prot can
be under memory stress.
Following are the results:
Estimated
Base Base Base
Benchmarks Ref. Run Time Ratio
mmotm with 500M
400.perlbench 9770 671 14.6 *
401.bzip2 9650 1011 9.55 *
403.gcc 8050 774 10.4 *
462.libquantum 20720 1213 17.1 *
mmot-prot with 500M
400.perlbench 9770 658 14.8 *
401.bzip2 9650 1007 9.58 *
403.gcc 8050 749 10.8 *
462.libquantum 20720 1116 18.6 *
mmotm with 4G ( allowing the full working sets)
400.perlbench 9770 594 16.5 *
401.bzip2 9650 828 11.7 *
403.gcc 8050 523 15.4 *
462.libquantum 20720 1121 18.5 *
It's worth noting that SPEC documented "The CPU2006 benchmarks
(code + workload) have been designed to fit within about 1GB of
physical memory",
and the exec vm sizes of these programs are as below:
perlbench 956KB
bzip2 56KB
gcc 3008KB
libquantum 36KB
Are we expecting to see more good results for cpu-bound programs (e.g.
scientific ones)
with large number of exec pages ?
Best Regards,
Nai Xia
On Mon, Jun 8, 2009 at 5:10 PM, Wu Fengguang<fengguang.wu@intel.com> wrote:
> Andrew,
>
> I managed to back this patchset with two test cases :)
>
> They demonstrated that
> - X desktop responsiveness can be *doubled* under high memory/swap pressure
> - it can almost stop major faults when the active file list is slowly scanned
> because of undergoing partially cache hot streaming IO
>
> The details are included in the changelog.
>
> Thanks,
> Fengguang
> --
>
> --
> 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>
>
--
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:[~2009-07-10 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 9:10 [PATCH 0/3] make mapped executable pages the first class citizen (with test cases) Wu Fengguang
2009-06-08 9:10 ` [PATCH 1/3] vmscan: report vm_flags in page_referenced() Wu Fengguang
2009-06-08 9:10 ` [PATCH 2/3] vmscan: make mapped executable pages the first class citizen Wu Fengguang
2009-06-08 15:34 ` Christoph Lameter
2009-06-08 17:30 ` Nai Xia
2009-06-09 3:28 ` Wu Fengguang
2009-06-08 9:10 ` [PATCH 3/3] vmscan: merge duplicate code in shrink_active_list() Wu Fengguang
2009-07-10 7:24 ` Nai Xia [this message]
2009-07-10 8:34 ` [PATCH 0/3] make mapped executable pages the first class citizen (with test cases) Wu Fengguang
2009-07-10 16:50 ` Nai Xia
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=ab418ea90907100024xe95ab44pb0809d262e616565@mail.gmail.com \
--to=nai.xia@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=cl@linux-foundation.org \
--cc=elladan@eskimo.com \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=npiggin@suse.de \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tytso@mit.edu \
/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).