From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andi Kleen <ak@suse.de>
Cc: jasonp@boo.net, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] page coloring for 2.5.59 kernel, version 1
Date: Tue, 28 Jan 2003 08:49:34 -0800 [thread overview]
Message-ID: <1498630000.1043772571@titus> (raw)
In-Reply-To: <p73k7gpz0vu.fsf@oldwotan.suse.de>
> The main advantage of cache coloring normally is that benchmarks
> should get stable results. Without it a benchmark result can vary based on
> random memory allocation patterns.
>
> Just having stable benchmarks may be worth it.
OK, I'll try to hack the scripts to measure standard deviation between runs
as well.
> I suspect the benefit will vary a lot based on the CPU. Your caches may
> have good enough associativity. On other CPUs it may make much more difference.
IIRC, P3's are 4 way associative ... people had been saying that this would
make more of a difference on machines with larger caches, which is why I ran
it ... 2Mb is fairly big for ia32.
M.
--
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:[~2003-01-28 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3.0.6.32.20030127224726.00806c20@boo.net.suse.lists.linux.kernel>
[not found] ` <884740000.1043737132@titus.suse.lists.linux.kernel>
[not found] ` <20030128071313.GH780@holomorphy.com.suse.lists.linux.kernel>
[not found] ` <1466000000.1043770007@titus.suse.lists.linux.kernel>
2003-01-28 16:37 ` Andi Kleen
2003-01-28 16:49 ` Martin J. Bligh [this message]
2003-01-28 17:06 ` Bill Davidsen
2003-01-28 17:22 ` Valdis.Kletnieks
2003-01-28 18:01 jasonp
-- strict thread matches above, loose matches on Subject: below --
2003-01-28 17:49 jasonp
2003-01-28 3:47 Jason Papadopoulos
2003-01-28 3:57 ` William Lee Irwin III
2003-01-28 4:11 ` William Lee Irwin III
2003-01-28 6:58 ` Martin J. Bligh
2003-01-28 7:13 ` William Lee Irwin III
2003-01-28 16:06 ` Martin J. Bligh
2003-01-28 16:41 ` Falk Hueffner
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=1498630000.1043772571@titus \
--to=mbligh@aracnet.com \
--cc=ak@suse.de \
--cc=jasonp@boo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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