All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
	bobby.prani@gmail.com
Subject: [PATCH tip/core/rcu 0/14] Documentation updates for 4.6
Date: Tue, 23 Feb 2016 21:00:21 -0800	[thread overview]
Message-ID: <20160224050021.GA14616@linux.vnet.ibm.com> (raw)

Hello!

This series contains documentation updates as follows:

1.	Update the requirements design-level documentation to record RCU's
	responsibility to avoid injecting OS jitter onto nohz_full CPUs.

2.	Fix control-dependency summary of memory-barriers.txt to
	note that barrier() does not always prevent code reordering
	when both legs of an "if" statement begin with identical code.

3.	Fix memory-barriers.txt section references.

4.	Update the requirements design-level documentation to add
	synchronize_rcu_mult().

5.	Remove obsolete references to RCU-protected array indexes from
	memory-barriers.txt.

6.	Update memory-barriers.txt to explicitly state that
	rcu_dereference() orders writes to as well as reads from
	the RCU-protected data item.

7.	Update memory-barriers.txt to distinguish between local and
	global transitivity.

8.	Update memory-barriers.txt to add alternative outcome from
	release-acquire chain.

9.	Add design-level documentation for RCU's major data structures.

10.	Update the requirements design-level documentation to explain
	why rcu_read_lock() needs no barrier() for PREEMPT=n.

11.	Remove misleading statement that transitivity is cumulativity
	from memory-barriers.txt.

12.	Update the requirements design-level documentation to explicitly
	state that it is illegal to invoke call_rcu() from an offline CPU.

13.	Add text to the design-level documentation for RCU's major data
	structures stating how the combining tree keeps lock contention
	under control.

14.	Clarify compiler store-fusion example in memory-barriers.txt.

							Thanx, Paul

------------------------------------------------------------------------

 RCU/Design/Data-Structures/BigTreeClassicRCU.svg            |  474 ++++
 RCU/Design/Data-Structures/BigTreeClassicRCUBH.svg          |  499 ++++
 RCU/Design/Data-Structures/BigTreeClassicRCUBHdyntick.svg   |  695 +++++
 RCU/Design/Data-Structures/BigTreePreemptRCUBHdyntick.svg   |  741 ++++++
 RCU/Design/Data-Structures/BigTreePreemptRCUBHdyntickCB.svg |  858 +++++++
 RCU/Design/Data-Structures/Data-Structures.html             | 1395 ++++++++++++
 RCU/Design/Data-Structures/Data-Structures.htmlx            | 1295 +++++++++++
 RCU/Design/Data-Structures/HugeTreeClassicRCU.svg           |  939 ++++++++
 RCU/Design/Data-Structures/TreeLevel.svg                    |  828 +++++++
 RCU/Design/Data-Structures/TreeMapping.svg                  |  305 ++
 RCU/Design/Data-Structures/TreeMappingLevel.svg             |  380 +++
 RCU/Design/Data-Structures/blkd_task.svg                    |  843 +++++++
 RCU/Design/Data-Structures/nxtlist.svg                      |  396 +++
 RCU/Design/Requirements/Requirements.html                   |  235 +-
 RCU/Design/Requirements/Requirements.htmlx                  |  121 +
 memory-barriers.txt                                         |  141 -
 16 files changed, 10074 insertions(+), 71 deletions(-)

             reply	other threads:[~2016-02-24  5:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  5:00 Paul E. McKenney [this message]
2016-02-24  5:00 ` [PATCH tip/core/rcu 01/14] documentation: Add real-time requirements from CPU-bound workloads Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 02/14] documentation: Fix control dependency and identical stores Paul E. McKenney
2016-02-24 21:12   ` Mathieu Desnoyers
2016-02-24 21:40     ` Paul E. McKenney
2016-02-25  6:41       ` Jianyu Zhan
2016-02-25 14:08         ` Paul E. McKenney
2016-02-25  8:21       ` Peter Zijlstra
2016-02-25 14:07         ` Paul E. McKenney
2016-02-25 14:48           ` Peter Zijlstra
2016-02-25 15:42             ` Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 03/14] documentation: Fix memory-barriers.txt section references Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 04/14] documentation: Add synchronize_rcu_mult() to the requirements Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 05/14] documentation: Remove obsolete reference to RCU-protected indexes Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 06/14] documentation: Subsequent writes ordered by rcu_dereference() Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 07/14] documentation: Distinguish between local and global transitivity Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 08/14] documentation: Add alternative release-acquire outcome Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 09/14] documentation: Add documentation for RCU's major data structures Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 10/14] documentation: Explain why rcu_read_lock() needs no barrier() Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 11/14] documentation: Transitivity is not cumulativity Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 12/14] documentation: Document illegality of call_rcu() from offline CPUs Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 13/14] documentation: Explain how RCU's combining tree fights contention Paul E. McKenney
2016-02-24  5:00 ` [PATCH tip/core/rcu 14/14] documentation: Clarify compiler store-fusion example 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=20160224050021.GA14616@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bobby.prani@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhart@linux.intel.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --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 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.