From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
hawkes@sgi.com, linux-kernel@vger.kernel.org, wli@holomorphy.com
Subject: Re: kernbench on 512p
Date: Thu, 19 Aug 2004 16:38:37 -0700 [thread overview]
Message-ID: <20040819233837.GA2723@us.ibm.com> (raw)
In-Reply-To: <200408191724.04422.jbarnes@engr.sgi.com>
On Thu, Aug 19, 2004 at 05:24:04PM -0400, Jesse Barnes wrote:
> On Thursday, August 19, 2004 5:11 pm, Jesse Barnes wrote:
> > The output is attached (my mailer insists on wrapping it if I inline it).
> > I used 'lockstat -w'.
>
> The highlights:
>
> nw spin rjct lock & function
> 19.0% 81.0% 0% dcache_lock
> 3.3% 96.7% 0% d_alloc+0x270
> 2.7% 97.3% 0% d_delete+0x40
> 18.3% 81.7% 0% d_instantiate+0x90
> 4.7% 95.3% 0% d_move+0x60
> 34.6% 65.4% 0% d_rehash+0xe0
> 19.1% 80.9% 0% dput+0x40
> 10.5% 89.5% 0% link_path_walk+0xef0
> 0% 100% 0% sys_getcwd+0x210
>
> 41.4% 58.6% 0% rcu_state
> 61.3% 38.7% 0% __rcu_process_callbacks+0x260
> 41.4% 58.6% 0% rcu_check_quiescent_state+0xf0
>
> So it looks like the dcache lock is the biggest problem on this system with
> this load. And although the rcu stuff has improved tremendously for this
> system, it's still highly contended.
Was this run using all of Manfred's RCU patches? If not, it would be
interesting to see what you get with full RCU_HUGE patchset.
Thanx, Paul
next prev parent reply other threads:[~2004-08-19 23:42 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 16:16 kernbench on 512p Jesse Barnes
2004-08-19 16:22 ` William Lee Irwin III
2004-08-19 16:29 ` David Mosberger
2004-08-19 16:37 ` Jesse Barnes
2004-08-19 16:40 ` David Mosberger
2004-08-19 17:55 ` Alan Cox
2004-08-20 7:53 ` David Mosberger
2004-08-19 18:25 ` Martin J. Bligh
2004-08-19 18:42 ` Jesse Barnes
2004-08-19 21:11 ` Jesse Barnes
2004-08-19 21:24 ` Jesse Barnes
2004-08-19 21:56 ` Martin J. Bligh
2004-08-20 19:36 ` Maneesh Soni
2004-08-19 23:38 ` Paul E. McKenney [this message]
2004-08-20 0:16 ` Jesse Barnes
2004-08-20 15:57 ` Paul E. McKenney
2004-08-20 17:24 ` Jesse Barnes
2004-08-20 19:22 ` Manfred Spraul
2004-08-20 20:19 ` Manfred Spraul
2004-08-23 21:23 ` Jesse Barnes
2004-08-23 23:13 ` Jesse Barnes
2004-09-10 19:01 ` Greg Edwards
2004-09-13 18:21 ` Manfred Spraul
2004-09-14 17:52 ` Greg Edwards
2004-09-14 18:16 ` Manfred Spraul
2004-09-14 18:43 ` Greg Edwards
2004-09-14 19:16 ` Manfred Spraul
2004-08-19 21:50 ` Ray Bryant
2004-08-19 22:00 ` Jesse Barnes
2004-08-19 23:03 ` William Lee Irwin III
2004-08-20 17:35 ` William Lee Irwin III
2004-08-20 0:56 ` remove dentry_open::file_ra_init_state() duplicated memset was " Marcelo Tosatti
2004-08-20 6:21 ` Andrew Morton
2004-08-20 7:28 ` Marcelo Tosatti
2004-08-20 8:34 ` Andrew Morton
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=20040819233837.GA2723@us.ibm.com \
--to=paulmck@us.ibm.com \
--cc=hawkes@sgi.com \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=wli@holomorphy.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