From: "Chris Friesen" <cfriesen@nortel.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: question on powerpc pthread mutexes and memory barriers
Date: Thu, 09 Jul 2009 16:42:56 -0600 [thread overview]
Message-ID: <4A567270.4040300@nortel.com> (raw)
In-Reply-To: <4A565EEB.9020607@nortel.com>
Chris Friesen wrote:
> Hi all,
>
> This probably isn't the right place to ask about this, but does anyone
> know where the implied memory barrier happens for pthread mutexes in the
> uncontended case? I'm looking at the glibc code and I don't see any
> barrier instructions for mutexes, only semaphores and spinlocks.
Bad form to follow up on my own question, but I tracked it down. The
barriers are there hidden in the atomic macros.
Sorry for the noise.
Chris
prev parent reply other threads:[~2009-07-09 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 21:19 question on powerpc pthread mutexes and memory barriers Chris Friesen
2009-07-09 22:42 ` Chris Friesen [this message]
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=4A567270.4040300@nortel.com \
--to=cfriesen@nortel.com \
--cc=linuxppc-dev@ozlabs.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.