From: David Howells <dhowells@redhat.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: dhowells@redhat.com, torvalds@osdl.org,
akpm@linux-foundation.org, sgruszka@redhat.com,
davem@davemloft.net, linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH] Document Linux's circular buffering capabilities
Date: Mon, 15 Mar 2010 12:36:05 +0000 [thread overview]
Message-ID: <30121.1268656565@redhat.com> (raw)
In-Reply-To: <4B9B5A37.2010206@s5r6.in-berlin.de>
Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> Would you agree to add a quick note that these examples are simple
> enough to not strictly require ACCESS_ONCE but are meant to show what
> more general code would have to do? Else a reader might be left puzzled
> why he can't see in the example code the circumstances which require
> ACCESS_ONCE and may remain unsure about where to use it in his own works...
How about adding a bit:
Note the use of ACCESS_ONCE() in both algorithms to read the opposition index.
This prevents the compiler from discarding and reloading its cached value -
-which some compilers will do across smp_read_barrier_depends().
+which some compilers will do across smp_read_barrier_depends(). This isn't
+strictly needed if you can be sure that the opposition index will _only_ be
+used the once.
David
next prev parent reply other threads:[~2010-03-15 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 17:20 [PATCH] Document Linux's circular buffering capabilities David Howells
2010-03-11 18:10 ` Randy Dunlap
2010-03-11 19:20 ` David Howells
2010-03-12 15:39 ` Stefan Richter
2010-03-12 23:41 ` David Howells
2010-03-13 9:26 ` Stefan Richter
2010-03-15 12:36 ` David Howells [this message]
2010-03-15 13:43 ` Stefan Richter
2010-03-15 13:55 ` David Howells
2010-03-15 14:16 ` Stefan Richter
2010-03-19 17:53 ` Mark Rustad
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=30121.1268656565@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rdunlap@xenotime.net \
--cc=sgruszka@redhat.com \
--cc=stefanr@s5r6.in-berlin.de \
--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 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.