From: Hanna Linder <hannal@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>,
Maneesh Soni <maneesh@in.ibm.com>, Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, viro@math.psu.edu
Cc: Hanna Linder <hannal@us.ibm.com>
Subject: Re: 2.5.36-mm1 dbench 512 profiles
Date: Fri, 20 Sep 2002 11:51:13 -0700 [thread overview]
Message-ID: <61200000.1032547873@w-hlinder> (raw)
In-Reply-To: <20020920120358.GV28202@holomorphy.com>
--On Friday, September 20, 2002 05:03:58 -0700 William Lee Irwin III <wli@holomorphy.com> wrote:
> On Fri, Sep 20, 2002 at 01:29:28PM +0530, Maneesh Soni wrote:
>>> For a 32-way system fastwalk will perform badly from dcache_lock
>>> point of view, basically due to increased lock hold time.
>>> dcache_rcu-12 should reduce dcache_lock contention and hold time. The
>>> patch uses RCU infrastructer patch and read_barrier_depends patch.
>>> The patches are available in Read-Copy-Update section on lse site at
>>> http://sourceforge.net/projects/lse
>
> On Fri, Sep 20, 2002 at 01:06:28AM -0700, William Lee Irwin III wrote:
>> ISTR Hubertus mentioning this at OLS, and it sounded like a problem to
>> me. I'm doing some runs with this to see if it fixes the problem.
I mentioned it at OLS too. It was the point of my talk. Next
time I will request a non 10am time slot!
> take its place. Ugly. OTOH the qualitative difference is striking. The
> interactive responsiveness of the machine, even when entirely unloaded,
> is drastically improved, along with such nice things as init scripts
> and kernel compiles also markedly faster. I suspect this is just the
> wrong benchmark to show throughput benefits with.
>
> Also notable is that the system time was significantly reduced though
> I didn't log it. Essentially a long period of 100% system time is
> entered after a certain point in the benchmark, during which there are
> few (around 60 or 70) context switches in a second, and the duration
> of this period was shortened.
Bill, you are saying that replacing dcache_rcu significantly
improved system response time among other things?
Perhaps it is time to reconsider replacing fastwalk with dcache_rcu.
Viro? What are your objections?
Thanks.
Hanna
next prev parent reply other threads:[~2002-09-20 18:41 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
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 [this message]
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=61200000.1032547873@w-hlinder \
--to=hannal@us.ibm.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--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 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.