From: Andrea Arcangeli <andrea@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Eric Whiting <ewhiting@amis.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: -mmX 4G patches feedback [numbers: how much performance impact]
Date: Wed, 7 Apr 2004 23:39:31 +0200 [thread overview]
Message-ID: <20040407213931.GN26888@dualathlon.random> (raw)
In-Reply-To: <20040407072517.GA32140@elte.hu>
On Wed, Apr 07, 2004 at 09:25:17AM +0200, Ingo Molnar wrote:
> but please be extremely careful with this testcase. It needs static
> linking & init= booting to produce stable, comparable numbers. I did
> this for a couple of key kernels and made sure the effect is the same as
> in the simple loop_print.c case, but it's a real PITA to ensure stable
> numbers.
you're basically testing the associativity of the TLB with your dTLB, no
surprise it gives very different results. the biggest noise generated by
page coloring is when the working set is equal the size of the cache,
for the tlb cache that's 64 pages on the prescott, but note I'm not
using a prescott, this is the first HT enabeld (P4 based) xeon I doubt
it has 64 dTLB entries, infact the biggest noise happens way below
256kbyte, I guess it has between 8 and 32 entries in the tlb (not sure
exactly, I've too old and too recent specifications none covering this
specific box, I didn't need to know this detail to benchmark accurately
and rule out page coloring by running multiple passes and verifiying
they're all the same).
next prev parent reply other threads:[~2004-04-07 21:39 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 16:36 -mmX 4G patches feedback Eric Whiting
2004-04-05 17:46 ` Andrea Arcangeli
2004-04-05 21:35 ` Eric Whiting
2004-04-05 22:16 ` Andrea Arcangeli
2004-04-06 11:55 ` -mmX 4G patches feedback [numbers: how much performance impact] Ingo Molnar
2004-04-06 14:49 ` Eric Whiting
2004-04-06 15:59 ` Andrea Arcangeli
2004-04-06 16:13 ` Arjan van de Ven
2004-04-06 16:39 ` Andrea Arcangeli
2004-04-06 17:24 ` Ingo Molnar
2004-04-06 17:57 ` Andrea Arcangeli
2004-04-07 22:54 ` Martin J. Bligh
2004-04-07 22:50 ` Andrea Arcangeli
2004-04-06 19:25 ` Ingo Molnar
2004-04-06 20:25 ` Andrea Arcangeli
2004-04-07 6:03 ` Andrea Arcangeli
2004-04-07 6:46 ` Ingo Molnar
2004-04-07 7:23 ` Andrea Arcangeli
2004-04-07 8:23 ` Ingo Molnar
2004-04-07 21:35 ` Andrea Arcangeli
2004-04-07 17:27 ` Andrea Arcangeli
2004-04-07 7:25 ` Ingo Molnar
2004-04-07 21:39 ` Andrea Arcangeli [this message]
2004-04-07 22:58 ` Martin J. Bligh
2004-04-07 23:01 ` Andrea Arcangeli
2004-04-07 23:21 ` Martin J. Bligh
2004-04-07 23:18 ` Andrea Arcangeli
2004-04-07 23:34 ` Martin J. Bligh
2004-04-08 0:18 ` Andrea Arcangeli
2004-04-08 6:24 ` Martin J. Bligh
2004-04-08 21:59 ` Andrea Arcangeli
2004-04-08 22:19 ` Martin J. Bligh
2004-04-08 22:19 ` Andrea Arcangeli
2004-04-08 23:14 ` Martin J. Bligh
2004-04-08 23:22 ` Andrea Arcangeli
2004-04-08 23:42 ` Martin J. Bligh
2004-04-08 23:49 ` Andrea Arcangeli
2004-04-07 21:19 ` -mmX 4G patches feedback Martin J. Bligh
2004-04-07 21:49 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2004-04-06 17:59 -mmX 4G patches feedback [numbers: how much performance impact] Manfred Spraul
2004-04-06 18:41 ` 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=20040407213931.GN26888@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=ewhiting@amis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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