mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Hanna Linder <hannal@us.ibm.com>
Cc: 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
Subject: Re: 2.5.36-mm1 dbench 512 profiles
Date: Sat, 21 Sep 2002 02:24:23 +0530	[thread overview]
Message-ID: <20020921022423.B5267@in.ibm.com> (raw)
In-Reply-To: <69960000.1032553974@w-hlinder>; from hannal@us.ibm.com on Fri, Sep 20, 2002 at 08:32:48PM +0000

On Fri, Sep 20, 2002 at 08:32:48PM +0000, Hanna Linder wrote:
> --On Friday, September 20, 2002 11:51:13 -0700 Hanna Linder <hannal@us.ibm.com> wrote:
> 
> > 
> > 	Perhaps it is time to reconsider replacing fastwalk with dcache_rcu. 
> 
> These patches were written by Maneesh Soni. Since the Read-Copy Update
> infrastructure has not been accepted into the mainline kernel yet (although
> there were murmurings of it being acceptable) you will need to apply
> those first. Here they are, apply in this order. Too big to post
> inline text though. These are provided against 2.5.36-mm1.
> 
> 
> http://prdownloads.sourceforge.net/lse/rcu_ltimer-2.5.36-mm1
> 
> http://prdownloads.sourceforge.net/lse/read_barrier_depends-2.5.36-mm1
> 
> http://prdownloads.sourceforge.net/lse/dcache_rcu-12-2.5.36-mm1
> 
> There has been quite a bit of testing done on this and it has proven
> quite stable. If anyone wants to do any additional testing that would
> be great.

Thanks for the vote of confidence :)

Now for some results (out of date, but also has results with backported code 
from 2.5) see http://lse.sf.net/locking/dcache/dcache.html.

Preliminary profiling of webserver benchmarks in 2.5.3X show similar potential
for dcache_rcu. I will have actual results published when we can
get formal runs done.

Thanks
-- 
Dipankar Sarma  <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.

  reply	other threads:[~2002-09-20 20:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 22:30 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
2002-09-20 20:32               ` Hanna Linder
2002-09-20 20:54                 ` Dipankar Sarma [this message]
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=20020921022423.B5267@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=akpm@digeo.com \
    --cc=hannal@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome