From: Arnd Bergmann <arnd@arndb.de>
To: paulmck@linux.vnet.ibm.com
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Herbert Xu <herbert@gondor.apana.org.au>,
csnook@redhat.com, dhowells@redhat.com,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
torvalds@linux-foundation.org, netdev@vger.kernel.org,
akpm@linux-foundation.org, ak@suse.de, heiko.carstens@de.ibm.com,
davem@davemloft.net, schwidefsky@de.ibm.com,
wensong@linux-vs.org, horms@verge.net.au, wjiang@resilience.com,
cfriesen@nortel.com, zlynx@acm.org, rpjday@mindspring.com,
jesper.juhl@gmail.com
Subject: Re: [PATCH 6/24] make atomic_read() behave consistently on frv
Date: Wed, 15 Aug 2007 15:29:43 +0200 [thread overview]
Message-ID: <200708151529.46780.arnd@arndb.de> (raw)
In-Reply-To: <20070814224354.GE8243@linux.vnet.ibm.com>
On Wednesday 15 August 2007, Paul E. McKenney wrote:
> ACCESS_ONCE() is indeed intended to be used when actually loading or
> storing the variable. That said, I must admit that it is not clear to me
> why you would want to add an extra order() rather than ACCESS_ONCE()ing
> one or both of the adjacent accesses to that same variable.
>
> So, what am I missing?
You're probably right, the only case I can construct is something like
if (ACCESS_ONCE(x)) {
...
ACCESS_ONCE(x)++;
}
which would be slightly less efficient than
if (x)
x++;
order(x);
because in the first case, you need to do two ordered accesses
but only one in the second case. However, I can't think of a case
where this actually makes a noticable difference in real life.
Arnd <><
next prev parent reply other threads:[~2007-08-15 14:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 13:41 [PATCH 6/24] make atomic_read() behave consistently on frv Chris Snook
2007-08-09 16:54 ` Chris Snook
2007-08-10 9:23 ` David Howells
2007-08-10 19:54 ` Chris Snook
2007-08-11 0:54 ` Herbert Xu
2007-08-11 0:54 ` Herbert Xu
2007-08-11 4:29 ` Paul E. McKenney
2007-08-13 5:15 ` Herbert Xu
2007-08-13 6:03 ` Paul E. McKenney
2007-08-14 5:34 ` Nick Piggin
2007-08-14 7:26 ` Herbert Xu
2007-08-14 17:01 ` Paul E. McKenney
2007-08-14 22:01 ` Arnd Bergmann
2007-08-14 22:43 ` Paul E. McKenney
2007-08-15 13:29 ` Arnd Bergmann [this message]
2007-08-15 15:06 ` Michael Buesch
2007-08-15 13:30 ` Nick Piggin
2007-08-15 20:15 ` Paul E. McKenney
2007-08-16 1:09 ` Nick Piggin
2007-08-16 2:27 ` Paul E. McKenney
2007-08-11 8:47 ` David Howells
2007-08-13 6:44 ` Chris Snook
2007-08-14 5:42 ` Nick Piggin
2007-08-15 18:51 ` Segher Boessenkool
2007-08-15 19:18 ` Paul E. McKenney
2007-08-15 19:46 ` Segher Boessenkool
2007-08-15 19:59 ` Paul E. McKenney
2007-08-15 20:13 ` Segher Boessenkool
2007-08-15 20:38 ` Paul E. McKenney
2007-08-15 21:15 ` Segher Boessenkool
2007-08-16 1:20 ` Nick Piggin
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=200708151529.46780.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=cfriesen@nortel.com \
--cc=csnook@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@verge.net.au \
--cc=jesper.juhl@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rpjday@mindspring.com \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=wensong@linux-vs.org \
--cc=wjiang@resilience.com \
--cc=zlynx@acm.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.