public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andi Kleen <ak@suse.de>
Cc: William Lee Irwin III <wli@holomorphy.com>,
	"David S. Miller" <davem@davemloft.net>,
	anton@samba.org, linux-arch@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>, Peter Keilty <Peter.Keilty@hp.com>
Subject: Re: Global spinlock vs local bit spin locks
Date: Fri, 17 Jun 2005 19:27:27 +1000	[thread overview]
Message-ID: <42B2977F.7040906@yahoo.com.au> (raw)
In-Reply-To: <20050617085426.GK31127@wotan.suse.de>

Andi Kleen wrote:
> On Fri, Jun 17, 2005 at 06:35:16PM +1000, Nick Piggin wrote:
> 
>>William Lee Irwin III wrote:
>>
>>
>>>I'd feel far more comfortable with this if the lockbit resided in the
>>>page. Also, compare it to akpm's solution.
>>>
>>
>>akpm's solution is alright. They perform similarly on the workload in
>>question. Of course, the bitlock will scale quite a lot better if you
>>pushed it and will automatically be localised per device and have NUMA
>>locality, etc.
> 
> 
> The buffer head is not necessarily NUMA local though - there is
> some chance that a BH from a different node is reused.

True, but compared to a hash which is almost guaranteed *not* to
be in local memory for any medium to large NUMA system :)

Though I guess on many, it is basically luck that you would get
an IO submitted on the same node that takes the completion
interrupt.

However, on really huge systems like SGI's, they often tend to
lock down devices and jobs quite tightly to nodes so I think
it has some merit.

-- 
SUSE Labs, Novell Inc.

Send instant messages to your online friends http://au.messenger.yahoo.com 

      parent reply	other threads:[~2005-06-17  9:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-17  4:21 Global spinlock vs local bit spin locks Nick Piggin
2005-06-17  4:45 ` Andrew Morton
2005-06-17  8:50   ` Andi Kleen
2005-06-17  4:45 ` David S. Miller
2005-06-17  4:46 ` William Lee Irwin III
2005-06-17  4:52   ` Andrew Morton
2005-06-17  8:35   ` Nick Piggin
2005-06-17  8:45     ` William Lee Irwin III
2005-06-17  9:21       ` Nick Piggin
2005-06-17  9:28         ` William Lee Irwin III
2005-06-17  8:54     ` Andi Kleen
2005-06-17  9:15       ` William Lee Irwin III
2005-06-17  9:27       ` Nick Piggin [this message]

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=42B2977F.7040906@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=Peter.Keilty@hp.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=davem@davemloft.net \
    --cc=linux-arch@vger.kernel.org \
    --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