From: Nick Piggin <nickpiggin@yahoo.com.au>
To: William Lee Irwin III <wli@holomorphy.com>
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: Fri, 17 Jun 2005 18:35:16 +1000 [thread overview]
Message-ID: <42B28B44.9090606@yahoo.com.au> (raw)
In-Reply-To: <20050617044611.GF3913@holomorphy.com>
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.
As far as page flags go - I agree but I didn't want to use one up.
This is very localised and I don't think it is particularly worse
than what was there before, so I think we can get away with it for
the moment.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-06-17 8:35 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 [this message]
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=42B28B44.9090606@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Peter.Keilty@hp.com \
--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