From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.69-mm8
Date: Fri, 23 May 2003 08:02:22 -0700 [thread overview]
Message-ID: <20030523150222.GC19818@holomorphy.com> (raw)
In-Reply-To: <26160000.1053700350@[10.10.2.4]>
At some point in the past, Dave Hansen removed Martin Bligh's attribution from:
>>> 1004 2.0% default_idle
>>> 272 8.3% __copy_from_user_ll
>>> 129 1.7% __d_lookup
>>> 79 7.5% link_path_walk
At some point in the past, Martin Bligh removed Dave Hansen's attribution from:
>> I have to wonder if these are cache effects, or just noise. Can you
>> give oprofile a try with one of the cache performance counters?
On Fri, May 23, 2003 at 07:32:31AM -0700, Martin J. Bligh wrote:
> No, but you can ;-)
Cache things are usually link order and .config dependent, in 2.4.x at
least they were highly dependent on cache color conflicts between task
structures and hot codepaths and similar bizarre phenomena. i.e. exact
binutils, compiler, kernel source, and .config matches are required to
reproduce. And sometimes even that isn't enough and it's not reproducible
across runs. You also want instruction-level multiplicative differential
profiling to find cacheline bounces, not function-level additive
differential profiling, with some method of correlating assembly to source.
-- wli
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-23 15:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 9:16 2.5.69-mm8 Andrew Morton
2003-05-22 12:05 ` 2.5.69-mm8 Philippe Gramoullé
2003-05-22 12:07 ` 2.5.69-mm8 Helge Hafting
2003-05-22 21:21 ` 2.5.69-mm8 Rudmer van Dijk
2003-05-22 14:55 ` 2.5.69-mm8 William Lee Irwin III
2003-05-22 17:13 ` 2.5.69-mm8 Alexander Hoogerhuis
2003-05-22 18:53 ` 2.5.69-mm8 Felipe Alfaro Solana
2003-05-22 19:30 ` 2.5.69-mm8 Paul Larson
2003-05-22 19:39 ` 2.5.69-mm8 Martin J. Bligh
2003-05-22 19:49 ` 2.5.69-mm8 Paul Larson
2003-05-22 21:03 ` 2.5.69-mm8 Dave Hansen
2003-05-22 20:14 ` 2.5.69-mm8 Andrew Morton
2003-05-22 21:19 ` 2.5.69-mm8 Paul Larson
2003-05-23 6:18 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 7:03 ` 2.5.69-mm8 Dave Hansen
2003-05-23 14:32 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 15:02 ` William Lee Irwin III [this message]
2003-05-23 15:31 ` 2.5.69-mm8 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=20030523150222.GC19818@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@digeo.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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