public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: David Howells <dhowells@redhat.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Dong Feng <middle.fengdong@gmail.com>,
	ak@suse.de, Paul Mackerras <paulus@samba.org>,
	Christoph Lameter <clameter@sgi.com>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Why Semaphore Hardware-Dependent?
Date: Wed, 13 Sep 2006 19:50:55 +0100	[thread overview]
Message-ID: <22461.1158173455@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <45084833.4040602@yahoo.com.au>

Nick Piggin <nickpiggin@yahoo.com.au> wrote:

> +	while ((tmp = atomic_read(&sem->count)) >= 0) {
> +		if (tmp == atomic_cmpxchg(&sem->count, tmp,
> +				   tmp + RWSEM_ACTIVE_READ_BIAS)) {

NAK for FRV.  Do not use atomic_cmpxchg() there as it isn't strictly atomic
(FRV only has one strictly atomic operation: SWAP).  Please leave FRV as using
the spinlock version which is more efficient on UP.

Please also show benchmarks to show the performance difference between your
version and the old version before Ingo messed it up and made everything
unconditionally out of line without cleaning the inline asm up.

If you are going to generalise, you should get rid of everything barring the
spinlock-based version and stick with that.  It will cost you performance
under some circumstances, but it's better under others than attempting to use
atomic_cmpxchg() which may not really exist on all archs.

You've also caused another problem: the spinlock based version permits up to
2^31 - 1 readers at one time, the inline optimised version, on a 32-bit arch,
will only permit up to 2^16 - 1 at most.  By doing this to x86_64, you've
reduced the number of processes it can support.

David

  parent reply	other threads:[~2006-09-13 18:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a2ebde260608271222x2b51693fnaa600965fcfaa6d2@mail.gmail.com>
     [not found] ` <1156750249.3034.155.camel@laptopd505.fenrus.org>
2006-08-29  1:18   ` Why Semaphore Hardware-Dependent? Nick Piggin
2006-08-29  6:07     ` Andi Kleen
2006-09-13 17:54       ` Nick Piggin
2006-08-29 10:05     ` David Howells
2006-08-29 10:56       ` Andi Kleen
2006-08-29 17:40         ` Andrew Morton
2006-08-29 19:10         ` Benjamin LaHaise
2006-08-29 15:56       ` Christoph Lameter
2006-08-29 16:20         ` Ralf Baechle
2006-08-29 16:25           ` David Howells
2006-08-29 16:28             ` Christoph Lameter
2006-08-29 16:57               ` David Howells
2006-08-29 16:53             ` Ralf Baechle
2006-08-29 16:58               ` Geert Uytterhoeven
2006-08-29 17:22         ` Andi Kleen
2006-08-29 17:36           ` Christoph Lameter
2006-08-29 18:18             ` Andi Kleen
2006-08-29 18:30               ` David Howells
2006-08-29 18:33                 ` Andi Kleen
2006-08-29 18:56                   ` David Howells
2006-08-29 18:41               ` Christoph Lameter
2006-09-13 18:04       ` Nick Piggin
2006-09-13 18:07         ` Christoph Lameter
2006-09-13 18:13           ` Nick Piggin
2006-09-13 18:16             ` Christoph Lameter
2006-09-13 18:50         ` David Howells [this message]
2006-09-13 19:25           ` Nick Piggin
2006-09-14 11:41             ` David Howells
2006-09-14 15:27               ` Nick Piggin
2006-09-14 15:38                 ` Nick Piggin
2006-09-15  8:59                 ` David Howells

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=22461.1158173455@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=ak@suse.de \
    --cc=arjan@infradead.org \
    --cc=clameter@sgi.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=middle.fengdong@gmail.com \
    --cc=nickpiggin@yahoo.com.au \
    --cc=paulus@samba.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