linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Ingo Molnar <mingo@elte.hu>,
	linux-arch@vger.kernel.org, linuxppc-dev@ozlabs.org,
	paulus@samba.org, benh@kernel.crashing.org
Subject: Re: [patch] powerpc: implement optimised mutex fastpaths
Date: Mon, 13 Oct 2008 03:18:27 +0200	[thread overview]
Message-ID: <20081013011827.GA1299@wotan.suse.de> (raw)
In-Reply-To: <20081012054732.GB12535@wotan.suse.de>

On Sun, Oct 12, 2008 at 07:47:32AM +0200, Nick Piggin wrote:
> 
> Implement a more optimal mutex fastpath for powerpc, making use of acquire
> and release barrier semantics. This takes the mutex lock+unlock benchmark
> from 203 to 173 cycles on a G5.
> 
> +static inline int
> +__mutex_fastpath_trylock(atomic_t *count, int (*fail_fn)(atomic_t *))
> +{
> +	if (likely(__mutex_cmpxchg_lock(count, 1, 0) == 1))
> +		return 1;

Oops, I must have sent the wrong version. This needs a return 0 here.

> +}

  reply	other threads:[~2008-10-13  1:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12  5:46 [patch] mutex: optimise generic mutex implementations Nick Piggin
2008-10-12  5:47 ` [patch] powerpc: implement optimised mutex fastpaths Nick Piggin
2008-10-13  1:18   ` Nick Piggin [this message]
2008-11-06  4:09     ` Paul Mackerras
2008-11-06  5:06       ` Nick Piggin
2008-10-13 16:15   ` Scott Wood
2008-10-13 16:20     ` Scott Wood
2008-10-14  7:06       ` Nick Piggin
2008-10-14  8:35 ` [patch] mutex: optimise generic mutex implementations Benjamin Herrenschmidt
2008-10-22 15:59 ` Ingo Molnar
2008-10-23  4:43   ` Benjamin Herrenschmidt
2008-10-23  7:02     ` Nick Piggin
2008-10-22 16:24 ` 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=20081013011827.GA1299@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@elte.hu \
    --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;
as well as URLs for NNTP newsgroup(s).