From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.69-mm8
Date: 23 May 2003 00:03:20 -0700 [thread overview]
Message-ID: <1053673399.1547.27.camel@nighthawk> (raw)
In-Reply-To: <17990000.1053670694@[10.10.2.4]>
On Thu, 2003-05-22 at 23:18, Martin J. Bligh wrote:
> 1004 2.0% default_idle
> 272 8.3% __copy_from_user_ll
> 129 1.7% __d_lookup
> 79 7.5% link_path_walk
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?
--
Dave Hansen
haveblue@us.ibm.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@digeo.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.69-mm8
Date: 23 May 2003 00:03:20 -0700 [thread overview]
Message-ID: <1053673399.1547.27.camel@nighthawk> (raw)
In-Reply-To: <17990000.1053670694@[10.10.2.4]>
On Thu, 2003-05-22 at 23:18, Martin J. Bligh wrote:
> 1004 2.0% default_idle
> 272 8.3% __copy_from_user_ll
> 129 1.7% __d_lookup
> 79 7.5% link_path_walk
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?
--
Dave Hansen
haveblue@us.ibm.com
--
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 6:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 9:16 2.5.69-mm8 Andrew Morton
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:05 ` 2.5.69-mm8 Philippe Gramoullé
2003-05-22 12:07 ` 2.5.69-mm8 Helge Hafting
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 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 14:55 ` 2.5.69-mm8 William Lee Irwin III
2003-05-22 17:13 ` 2.5.69-mm8 Alexander Hoogerhuis
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 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: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 21:03 ` 2.5.69-mm8 Dave Hansen
2003-05-22 20:14 ` 2.5.69-mm8 Andrew Morton
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 6:18 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 7:03 ` Dave Hansen [this message]
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 14:32 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 15:02 ` 2.5.69-mm8 William Lee Irwin III
2003-05-23 15:02 ` 2.5.69-mm8 William Lee Irwin III
2003-05-23 15:31 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 15:31 ` 2.5.69-mm8 Martin J. Bligh
2003-05-23 17:23 ` 2.5.69-mm8 Arador
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=1053673399.1547.27.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=akpm@digeo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.