linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Linder <hannal@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Cc: Hanna Linder <hannal@us.ibm.com>, viro@math.psu.edu
Subject: Re: 2.5.36-mm1 dbench 512 profiles
Date: Thu, 19 Sep 2002 16:18:38 -0700	[thread overview]
Message-ID: <68630000.1032477517@w-hlinder> (raw)
In-Reply-To: <20020919223007.GP28202@holomorphy.com>

--On Thursday, September 19, 2002 15:30:07 -0700 William Lee Irwin III <wli@holomorphy.com> wrote:

> From dbench 512 on a 32x NUMA-Q with 32GB of RAM running 2.5.36-mm1:
> 
> c015c5c6 4243413  10.742      .text.lock.dcache
> c01317f4 2229431  5.64371     generic_file_write_nolock
> c0130d10 2182906  5.52593     file_read_actor
> c0114f30 2126191  5.38236     scheduler_tick
> c0154b83 1905648  4.82407     .text.lock.namei
> c011749d 1344623  3.40386     .text.lock.sched
> c019f8ab 1102566  2.7911      .text.lock.dec_and_lock
> c01066a8 612167   1.54968     .text.lock.semaphore
> c015ba5c 440889   1.11609     d_lookup

> 
> with akpm's removal of lock section directives:
> 
> c0114de0 6545861  7.89765     scheduler_tick
> c0151718 4514372  5.44664     path_lookup
> c015ac4c 3314721  3.99924     d_lookup
> c0130560 3153290  3.80448     file_read_actor
> c0131044 2816477  3.39811     generic_file_write_nolock
> c015a8e4 1980809  2.38987     d_instantiate
> c019e1b0 1959187  2.36378     atomic_dec_and_lock
> c0111668 1447604  1.74655     smp_apic_timer_interrupt
> c0159fc0 1291884  1.55867     prune_dcache
> c015a714 1089696  1.31473     d_alloc
> c01062cc 1030194  1.24294     __down

	So akpm's removal of lock section directives breaks down the
functions holding locks that previously were reported under the 
.text.lock.filename?  Looks like fastwalk might not behave so well
on this 32 cpu numa system...

Hanna


  reply	other threads:[~2002-09-19 23:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 22:30 2.5.36-mm1 dbench 512 profiles William Lee Irwin III
2002-09-19 23:18 ` Hanna Linder [this message]
2002-09-19 23:38   ` Andrew Morton
2002-09-19 23:45     ` Hanna Linder
2002-09-20  0:08     ` William Lee Irwin III
2002-09-20  4:02       ` William Lee Irwin III
2002-09-20  7:59       ` Maneesh Soni
2002-09-20  8:06         ` William Lee Irwin III
2002-09-20 12:03           ` William Lee Irwin III
2002-09-20 18:51             ` Hanna Linder
2002-09-20 20:32               ` Hanna Linder
2002-09-20 20:54                 ` Dipankar Sarma
2002-09-20 20:39               ` William Lee Irwin III
2002-09-20 21:30             ` Martin J. Bligh
2002-09-20 23:11               ` William Lee Irwin III
2002-09-20 23:22                 ` Martin J. Bligh
2002-09-21  7:52             ` William Lee Irwin III
2002-09-20 14:34         ` Dave Hansen
2002-09-20 16:07           ` Martin J. Bligh
2002-09-20 17:48             ` Dipankar Sarma
2002-09-20 17:40           ` Dipankar Sarma
2002-09-20 20:28             ` Dipankar Sarma
2002-09-20  5:14     ` William Lee Irwin III
2002-09-20  6:59     ` William Lee Irwin III

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=68630000.1032477517@w-hlinder \
    --to=hannal@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    --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;
as well as URLs for NNTP newsgroup(s).