From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: David Howells <dhowells@redhat.com>
Cc: 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: Sat, 13 Mar 2010 10:26:15 +0100 [thread overview]
Message-ID: <4B9B5A37.2010206@s5r6.in-berlin.de> (raw)
In-Reply-To: <18180.1268437268@redhat.com>
David Howells wrote:
> Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>> "...do this" could be misunderstood as "use a modulus instruction",
...
> How about:
>
> Calculation of the occupancy or the remaining capacity of an
> arbitrarily sized circular buffer would normally be a slow operation,
> requiring the use of a modulus (divide) instruction. However, if the
> buffer is of a power-of-2 size,
[...]
Yep.
>> I don't understand why ACCESS_ONCE is needed here. The CIRC_SPACE and
>> CIRC_CNT macros do not look at head and tail more than once.
>
> In this example they don't, but say someone wants to read several elements
> from the buffer, they might end up accessing their copy of head several times.
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...
(BTW, good that I came across your documentation posting. This twist
with possibly multiple loads was not apparent to me too. I am going to
have to have another look at some driver code with this in mind...)
--
Stefan Richter
-=====-==-=- --== -==-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2010-03-13 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 17:20 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 [this message]
2010-03-15 12:36 ` David Howells
2010-03-15 13:43 ` Stefan Richter
2010-03-19 17:53 ` Mark Rustad
2010-03-15 13:55 ` David Howells
2010-03-15 14:16 ` Stefan Richter
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=4B9B5A37.2010206@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rdunlap@xenotime.net \
--cc=sgruszka@redhat.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
all inboxes | Powered by JetHome®