From: David Howells <dhowells@redhat.com>
To: paulmck@us.ibm.com, davem@redhat.com
Cc: akpm@osdl.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
linuxppc64-dev@ozlabs.org
Subject: Re: [PATCH] Document Linux's memory barriers [try #5]
Date: Thu, 23 Mar 2006 18:34:27 +0000 [thread overview]
Message-ID: <895.1143138867@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20060316231723.GB1323@us.ibm.com>
Paul E. McKenney <paulmck@us.ibm.com> wrote:
> smp_mb__before_atomic_dec() and friends as well?
These seem to be something Sparc64 related; or, at least, Sparc64 seems to do
something weird with them.
What are these meant to achieve anyway? They seems to just be barrier() on a
lot of systems, even SMP ones.
> Some architectures have more expansive definition of data dependency,
> including then- and else-clauses being data-dependent on the if-condition,
> but this is probably too much detail.
Linus calls that a "control dependency" and doesn't seem to think that's a
problem as it's sorted out by branch prediction. What you said makes me
wonder about conditional instructions (such as conditional move).
Anyway, I've incorporated your comments as well as reworking the document,
which I'll shortly push upstream once again.
David
next parent reply other threads:[~2006-03-23 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060316231723.GB1323@us.ibm.com>
[not found] ` <16835.1141936162@warthog.cambridge.redhat.com>
[not found] ` <18351.1142432599@warthog.cambridge.redhat.com>
2006-03-23 18:34 ` David Howells [this message]
2006-03-23 19:28 ` [PATCH] Document Linux's memory barriers [try #5] Linus Torvalds
2006-03-23 22:26 ` Paul E. McKenney
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=895.1143138867@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulmck@us.ibm.com \
--cc=torvalds@osdl.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).