From: Ralf Baechle <ralf@linux-mips.org>
To: "Gideon Stupp (gstupp)" <gstupp@cisco.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Sync operation in atomic_add_return()
Date: Fri, 10 Nov 2006 13:37:19 +0000 [thread overview]
Message-ID: <20061110133719.GA10119@linux-mips.org> (raw)
In-Reply-To: <E98CBCB9ACC07244969BE4541EC0A78303137105@xmb-ams-33b.emea.cisco.com>
On Mon, Nov 06, 2006 at 03:42:32PM +0100, Gideon Stupp (gstupp) wrote:
> I am trying to figure out why there is a sync operation in
> linux/include/asm-mips/atomic.h:atomic_add_return().
> I believe it was added in the linux-2.4.19 patch, but can't trace the
> reason. Can anyone help?
MIPS is a weakly ordered architecture. In theory. So those syncs are
required to ensure proper global ordering. In practice only the Sibyte
SB1 and RM9000 CMPs are documented to be weakly ordered but I've never
actually observed a single reordering related bug on any MIPS
multiprocessor which may either mean no reordering happens in practice
or I'm a genious managed to fix all reordering related bugs before they
could strike. I tend to assume the latter ;-) On a uniprocessor these
syncs are definately not needed and I have a patch to remove the sync
for uniprocessor kernels and known to be strongly ordered SMPs waiting
for 2.6.20.
Ralf
next prev parent reply other threads:[~2006-11-10 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 14:42 Sync operation in atomic_add_return() Gideon Stupp (gstupp)
2006-11-06 14:42 ` Gideon Stupp (gstupp)
2006-11-10 13:37 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-06 18:17 Kaz Kylheku
2006-11-06 18:17 ` Kaz Kylheku
2006-11-10 13:50 ` Ralf Baechle
2006-11-12 6:46 Gideon Stupp (gstupp)
2006-11-12 6:46 ` Gideon Stupp (gstupp)
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=20061110133719.GA10119@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=gstupp@cisco.com \
--cc=linux-mips@linux-mips.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