From: "Chris Friesen" <cfriesen@nortel.com>
To: sparclinux@vger.kernel.org
Subject: memory barriers on sparc
Date: Mon, 25 Jan 2010 18:53:32 +0000 [thread overview]
Message-ID: <4B5DE8AC.7040606@nortel.com> (raw)
Someone asked a question on comp.programming.threads about memory
barriers, which led me to the discovery that glibc and the kernel use
different semantics for memory barriers on sparc64 (and maybe sparc too,
didn't check).
The kernel uses:
read : LoadLoad
write : StoreStore
This matches my understanding of the behaviour of other architectures as
well. I got confused when I saw that glibc (as of 2.8 at least) uses:
read: LoadLoad | LoadStore
write: StoreLoad | StoreStore
I'm curious about the difference. Could someone explain why glibc uses
additional restrictions and the kernel doesn't?
Thanks,
Chris
next reply other threads:[~2010-01-25 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 18:53 Chris Friesen [this message]
2010-01-25 21:27 ` memory barriers on sparc David Miller
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=4B5DE8AC.7040606@nortel.com \
--to=cfriesen@nortel.com \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.