All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: "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: Thu, 16 Jun 2005 21:46:11 -0700	[thread overview]
Message-ID: <20050617044611.GF3913@holomorphy.com> (raw)
In-Reply-To: <1118982092.5261.44.camel@npiggin-nld.site>

On Fri, Jun 17, 2005 at 02:21:32PM +1000, Nick Piggin wrote:
> Peter Keilty is running into some scalability problems with buffer
> head based IO. There are a couple of global spinlocks in the buffer
> completion path, and they're showing up on 16-way IA64 systems.
> Replacing these locks with a bit spin lock in the buffer head status
> field has been shown to eliminate the bouncing problem. We want to
> go with this unless anyone has an objection to the cost.
> There is a cost (though I haven't been able to measure a signficant
> change), but I think it will be outweighed by the the reduction in
> cacheline contention on even small SMPs doing IO.
> Any input would be appreciated.
> If anyone wants to run some tests, possibly the easiest would be to
> make ext2 on loopback on tmpfs (to test scalability, have one loop
> device for each CPU in the system and bind the loop threads to each
> CPU). Make sure ext2 block size is < PAGE_SIZE.

I'd feel far more comfortable with this if the lockbit resided in the
page. Also, compare it to akpm's solution.


-- wli

  parent reply	other threads:[~2005-06-17  4:46 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 [this message]
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

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=20050617044611.GF3913@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=Peter.Keilty@hp.com \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=davem@davemloft.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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.