From: Thiemo Seufer <ths@networkno.de>
To: David Daney <ddaney@avtrex.com>
Cc: Richard Sandiford <rsandifo@nildram.co.uk>,
GCC Mailing List <gcc@gcc.gnu.org>,
linux-mips@linux-mips.org
Subject: Re: MIPS atomic memory operations (A.K.A PR 33479).
Date: Wed, 19 Sep 2007 09:45:15 +0100 [thread overview]
Message-ID: <20070919084515.GM9972@networkno.de> (raw)
In-Reply-To: <46F06980.4080500@avtrex.com>
David Daney wrote:
> Richard,
>
> There seems to be a small problem with the MIPS atomic memory operations
> patch I recently committed
> (http://gcc.gnu.org/ml/gcc-patches/2007-08/msg01290.html), in that on a
> dual CPU machine it does not quite work.
>
> You can look at http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33479#c3 for
> more information.
>
> Here is the code in question (from mips.h):
>
> #define MIPS_COMPARE_AND_SWAP(SUFFIX, OP) \
> "%(%<%[sync\n" \
This sync is for SB-1 implied by ll, but other MIPS systems may
need it.
> "1:\tll" SUFFIX "\t%0,%1\n" \
> "\tbne\t%0,%2,2f\n" \
> "\t" OP "\t%@,%3\n" \
> "\tsc" SUFFIX "\t%@,%1\n" \
> "\tbeq\t%@,%.,1b\n" \
> "\tnop\n" \
The SB-1 needs a "sync" here.
> "2:%]%>%)"
>
>
>
> I guess my basic question is: Should MIPS_COMPARE_AND_SWAP have a 'sync'
> after the 'sc'? I would have thought that 'sc' made the write visible to
> all CPUs, but on the SB1 it appears not to be the case.
>
> If we do need to add another 'sync' should it go in the delay slot of the
> branch? I would say yes because we would expect the branch to rarely
> taken.
But it would make things a lot worse for the contended case, which is
the interesting one for performance.
Thiemo
next prev parent reply other threads:[~2007-09-19 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 0:12 MIPS atomic memory operations (A.K.A PR 33479) David Daney
2007-09-19 2:32 ` Daniel Jacobowitz
2007-09-19 8:45 ` Thiemo Seufer [this message]
2007-09-19 16:58 ` Ralf Baechle
2007-09-19 17:07 ` Maciej W. Rozycki
2007-09-19 17:26 ` David Daney
2007-09-19 17:46 ` Maciej W. Rozycki
2007-09-19 17:49 ` David Daney
2007-09-19 18:12 ` Thiemo Seufer
2007-09-19 18:28 ` Ralf Baechle
2007-09-19 17:47 ` David Daney
2007-09-19 18:08 ` Maciej W. Rozycki
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=20070919084515.GM9972@networkno.de \
--to=ths@networkno.de \
--cc=ddaney@avtrex.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-mips@linux-mips.org \
--cc=rsandifo@nildram.co.uk \
/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