All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 67-mjb2 vs 68-mjb1 (sdet degredation)
Date: Mon, 21 Apr 2003 20:52:31 -0700	[thread overview]
Message-ID: <20030421205231.4392aaa7.akpm@digeo.com> (raw)
In-Reply-To: <147950000.1050981750@[10.10.2.4]>

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> > Here's a backout patch.  Does it fix it up?
> 
> Yeah, that fixes it. Ho hum ... I wonder if we can find something that
> works well for both cases? I guess the options would be:
> 
> 1. Some way to make the rwlock mechanism itself faster.
> 2. Try to fix the contention itself somehow for this instance.

You're using PIII's, which don't mind the additional buslocked operation. 
P4's hate it.  We'd need to retest on big P4 and other architectures to
decide.

I suspect the spinlock is better that the rwlock overall - having multiple
CPUs looking up things in the same address_space is relatively uncommon. 
Having one CPU looking things up in one address space is very common, and
that's the thing which the s/rwlock/spinlock/ speeds up.


  reply	other threads:[~2003-04-22  3:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-21 21:12 67-mjb2 vs 68-mjb1 (sdet degredation) Martin J. Bligh
2003-04-21 21:46 ` Andrew Morton
2003-04-21 22:55   ` William Lee Irwin III
2003-04-22  3:22   ` Martin J. Bligh
2003-04-22  3:52     ` Andrew Morton [this message]
2003-04-22  4:14       ` Martin J. Bligh
2003-04-22  4:06     ` Martin J. Bligh

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=20030421205231.4392aaa7.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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.