From: smuckle@codeaurora.org (Steve Muckle)
To: linux-arm-kernel@lists.infradead.org
Subject: barriers in mutexes?
Date: Wed, 02 Feb 2011 18:05:46 -0800 [thread overview]
Message-ID: <4D4A0D7A.9090005@codeaurora.org> (raw)
Hello,
Looking at kernel/mutex.c and arch/arm/include/asm/mutex.h, it appears
there aren't any memory barriers in the fast path of mutexes. I see this
was discussed here a long time back:
http://patchwork.kernel.org/patch/25856/
How was this resolved?
thanks,
Steve
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2011-02-03 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 2:05 Steve Muckle [this message]
2011-02-03 11:08 ` barriers in mutexes? Russell King - ARM Linux
2011-02-03 16:56 ` Steve Muckle
2011-02-20 13:14 ` Russell King - ARM Linux
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=4D4A0D7A.9090005@codeaurora.org \
--to=smuckle@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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).