linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
	niv@us.ibm.com, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	darren@dvhart.com, fweisbec@gmail.com, sbw@mit.edu
Subject: Re: [PATCH tip/core/rcu 2/3] rcu: Update RTFP documentation
Date: Sat, 17 Aug 2013 19:46:30 -0700	[thread overview]
Message-ID: <20130818024630.GA28923@leaf> (raw)
In-Reply-To: <1376789153-27138-2-git-send-email-paulmck@linux.vnet.ibm.com>

On Sat, Aug 17, 2013 at 06:25:52PM -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>

Could you mention the BibTeX formatting changes (and the rationale for
them) in the commit message, please?

> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>

A couple of comments below (and above); with those fixed,
Reviewed-by: Josh Triplett <josh@joshtriplett.org>

> ---
>  Documentation/RCU/RTFP.txt | 855 +++++++++++++++++++++++++++++----------------
>  1 file changed, 550 insertions(+), 305 deletions(-)
> 
> diff --git a/Documentation/RCU/RTFP.txt b/Documentation/RCU/RTFP.txt
> index 7f40c72..350be9a 100644
> --- a/Documentation/RCU/RTFP.txt
> +++ b/Documentation/RCU/RTFP.txt
> @@ -39,7 +39,7 @@ in read-mostly situations.  This algorithm does take pains to avoid
>  write-side contention and parallelize the other write-side overheads by
>  providing a fine-grained locking design, however, it would be interesting
>  to see how much of the performance advantage reported in 1990 remains
> -in 2004.
> +in 2004 (to say nothing of 2013).

In lieu of updating this again in 9 years, s/2004.*/today./ please?

> +In 2012, Josh Triplett received his Ph.D. with his dissertation
> +covering RCU-protected resizable hash tables and the relationship
> +between memory barriers and read-side traversal order:  If the updater
> +is making changes in the opposite direction from the read-side traveral
> +order, the updater need only execute a memory-barrier instruction,
> +but if in the same direction, the updater needs to wait for a grace
> +period between the individual updates [JoshTriplettPhD].  Also in 2012,

:)

> +after seventeen years of attempts, an RCU paper made it into a top-flight
> +academic journal, IEEE Transactions on Parallel and Distributed Systems
> +[MathieuDesnoyers2012URCU].  A group of researchers in Spain applied

What about the 2010 paper in Operating Systems Review?

> +user-level RCU to crowd simulation [GuillermoVigueras2012RCUCrowd], and
> +another group of researchers in Europe produced a formal description of
> +RCU based on separation logic [AlexeyGotsman2012VerifyGraceExtended],

Oh, interesting, I hadn't seen that one yet.

> +@phdthesis{JoshTriplettPhD
> +,author="Josh Triplett"
> +,title="Relativistic Causal Ordering A Memory Model for Scalable Concurrent Data Structures"

"A Memory Model ..." is a subtitle, so there should be either a : or a
--- after "Ordering".

> +,school="Portland State University"
> +,year="2012"
> +,annotation={
> +	RCU-protected hash tables, barriers vs. read-side traversal order.
> +}

Consider duplicating the summary above about traversal order versus
update order, and memory barriers versus grace periods, into the
annotation.

> +@article{GuillermoVigueras2012RCUCrowd
> +,author = {Vigueras, Guillermo and Ordu\~{n}a, Juan M. and Lozano, Miguel}
> +,citeulike-article-id = {10632151}
> +,citeulike-linkout-0 = {http://dx.doi.org/10.1007/s11227-012-0766-x}
> +,citeulike-linkout-1 = {http://www.springerlink.com/content/25762r0874163570}

Consider dropping these non-standard BibTeX tags; nothing will ever
format them, and you already have the doi below.

> +,day = {25}
> +,doi = {10.1007/s11227-012-0766-x}
> +,issn = {0920-8542}
> +,journal = {The Journal of Supercomputing}
> +,keywords = {linux, simulation}
> +,month = apr
> +,posted-at = {2012-05-03 09:12:04}
> +,priority = {2}
> +,title = {{A Read-Copy Update based parallel server for distributed crowd simulations}}
> +,url = {http://dx.doi.org/10.1007/s11227-012-0766-x}
> +,year = {2012}
> +}
> +
> +
> +@unpublished{JonCorbet2012ACCESS:ONCE

LWN is not "unpublished"; it's at least "misc", and I'd suggest
"article".  Ditto for every other LWN cite in this bibliography.

> +,Author="Jon Corbet"
> +,Title="{ACCESS\_ONCE()}"
> +,month="August"
> +,day="1"
> +,year="2012"
> +,note="\url{http://lwn.net/Articles/508991/}"
> +,annotation={
> +	A couple of simple specific compiler optimizations that motivate
> +	ACCESS_ONCE().
> +}
> +}

- Josh Triplett

  reply	other threads:[~2013-08-18  2:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18  1:25 [PATCH tip/core/rcu 0/3] Documentation updates for 3.12 Paul E. McKenney
2013-08-18  1:25 ` [PATCH tip/core/rcu 1/3] rcu: Fix rcu_barrier() documentation Paul E. McKenney
2013-08-18  1:25   ` [PATCH tip/core/rcu 2/3] rcu: Update RTFP documentation Paul E. McKenney
2013-08-18  2:46     ` Josh Triplett [this message]
2013-08-19  0:20       ` Paul E. McKenney
2013-08-19  0:38         ` Josh Triplett
2013-08-19  4:09           ` Paul E. McKenney
2013-08-18  1:25   ` [PATCH tip/core/rcu 3/3] doc: Fix memory-barrier control-dependency example Paul E. McKenney
2013-08-18  2:47 ` [PATCH tip/core/rcu 0/3] Documentation updates for 3.12 Josh Triplett
2013-08-20  7:09 ` Rob Landley
2013-08-20 13:39   ` Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2013-08-20  2:37 [PATCH tip/core/rcu 0/3] v2 " Paul E. McKenney
2013-08-20  2:37 ` [PATCH tip/core/rcu 1/3] rcu: Fix rcu_barrier() documentation Paul E. McKenney
2013-08-20  2:37   ` [PATCH tip/core/rcu 2/3] rcu: Update RTFP documentation Paul E. McKenney
2013-08-20  3:22     ` Josh Triplett

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=20130818024630.GA28923@leaf \
    --to=josh@joshtriplett.org \
    --cc=akpm@linux-foundation.org \
    --cc=darren@dvhart.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sbw@mit.edu \
    --cc=tglx@linutronix.de \
    /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).