From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Fix ia64 bit ops: Full barriers for bit operations returning a value
Date: Tue, 04 Apr 2006 13:30:34 +0000 [thread overview]
Message-ID: <200604041329.k34DTRx03774@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604031129510.21064@schroedinger.engr.sgi.com>
Christoph Lameter wrote on Monday, April 03, 2006 7:12 PM
> On Mon, 3 Apr 2006, Chen, Kenneth W wrote:
>
> > Looks good to me.
> > Acked-by: Ken Chen <kenneth.w.chen@intel.com>
>
> Ummm.. Are you sure? The release should come before the acquire. The
> final store of the cmpxchg may be delayed until after stores following
> the cmpxchg?
I realized that. However, this patch is one step forward to fix current
deficiency even if it is not a full solution. Hence the ack. I also take
that as your intention to post this patch as well, no?
- Ken
next prev parent reply other threads:[~2006-04-04 13:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 18:32 Fix ia64 bit ops: Full barriers for bit operations returning a value Christoph Lameter
2006-04-03 23:11 ` Chen, Kenneth W
2006-04-04 1:05 ` Fix ia64 bit ops: Full barriers for bit operations returning Nick Piggin
2006-04-04 2:11 ` Fix ia64 bit ops: Full barriers for bit operations returning a Christoph Lameter
2006-04-04 13:30 ` Chen, Kenneth W [this message]
2006-04-04 14:40 ` Christoph Lameter
2006-04-04 16:48 ` Fix ia64 bit ops: Full barriers for bit operations returning Zoltan Menyhart
2006-04-05 15:30 ` Zoltan Menyhart
2006-04-05 16:17 ` Fix ia64 bit ops: Full barriers for bit operations returning a Christoph Lameter
2006-04-05 16:44 ` Fix ia64 bit ops: Full barriers for bit operations returning Zoltan Menyhart
2006-04-05 17:31 ` Fix ia64 bit ops: Full barriers for bit operations returning a Christoph Lameter
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=200604041329.k34DTRx03774@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox