public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Mallick, Asit K" <asit.k.mallick@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] don't use ld.bias
Date: Wed, 23 Jul 2003 04:40:02 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105893522123205@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105883179830025@msgid-missing>

It does make sense to not use the ld.bias in the spinlock, it will make
more cacheline bouncing in a larger SMP system.
Thanks,
Asit


> -----Original Message-----
> From: Jesse Barnes [mailto:jbarnes@sgi.com] 
> Sent: Tuesday, July 22, 2003 6:12 AM
> To: Chen, Kenneth W
> Cc: linux-ia64@vger.kernel.org; davidm@hpl.hp.com
> Subject: Re: [PATCH] don't use ld.bias
> 
> 
> On Mon, Jul 21, 2003 at 05:15:39PM -0700, Chen, Kenneth W wrote:
> > > Patch to fix spin_lock to not use ld.bias since it causes 
> a bunch of
> > bus
> > > activity that hurts scalability when a lock is contended.
> > 
> > It's dangerous to say something without knowing the whole 
> context, but I
> > can't resist asking why not fix the contended lock area 
> instead?  Sounds
> > like you have some serious contention.
> 
> Maybe I shouldn't have said 'contended'.  This causes 
> problems even when
> a lock is nearly uncontended.  I agree that fixing lock 
> contention is a
> good idea, but as I read this code, it'll only make the very best case
> (totally uncontended) only a little better than if the 
> ld.bias were just
> an ld and it makes the average and contended cases _much_ worse.
> 
> I can get some data if you're not convinced by reading the code :)
> 
> Thanks,
> Jesse
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  parent reply	other threads:[~2003-07-23  4:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 23:55 [PATCH] don't use ld.bias Jesse Barnes
2003-07-22  0:15 ` Chen, Kenneth W
2003-07-22 13:11 ` Jesse Barnes
2003-07-23  4:40 ` Mallick, Asit K [this message]
2003-07-23 12:00 ` Matthew Wilcox
2003-07-25  1:10 ` David Mosberger
2003-07-25 13:40 ` Jesse Barnes

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=marc-linux-ia64-105893522123205@msgid-missing \
    --to=asit.k.mallick@intel.com \
    --cc=linux-ia64@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