public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernbench on 512p
Date: Thu, 19 Aug 2004 09:22:31 -0700	[thread overview]
Message-ID: <20040819162231.GS11200@holomorphy.com> (raw)
In-Reply-To: <200408191216.33667.jbarnes@engr.sgi.com>

On Thu, Aug 19, 2004 at 12:16:33PM -0400, Jesse Barnes wrote:
> Here's the kernel profile.  It would be nice if the patch to show which lock 
> is contended got included.  I think it was discussed awhile back, but I don't 
> have one against the newly merged profiling code.
> [root@ascender root]# readprofile -m System.map | sort -nr | head -30
> 208218076 total                                     30.1677
> 90036167 ia64_pal_call_static                     468938.3698
> 88140492 default_idle                             229532.5312
> 10312592 ia64_save_scratch_fpregs                 161134.2500
> 10306777 ia64_load_scratch_fpregs                 161043.3906
> 8723555 ia64_spinlock_contention                 90870.3646
> 121385 rcu_check_quiescent_state                316.1068
>  40464 file_move                                180.6429
>  32374 file_kill                                144.5268
>  25316 atomic_dec_and_lock                       98.8906
>  24814 clear_page                               155.0875
>  17709 file_ra_state_init                       110.6813
>  17603 clear_page_tables                         13.4169

file_move()? file_kill()? I smell files_lock.


-- wli

  reply	other threads:[~2004-08-19 16:22 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 [this message]
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
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=20040819162231.GS11200@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.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