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,
fweisbec@gmail.com, oleg@redhat.com
Subject: [PATCH tip/core/rcu 0/16] Documentation updates for v4.15
Date: Wed, 4 Oct 2017 14:20:51 -0700 [thread overview]
Message-ID: <20171004212051.GA8411@linux.vnet.ibm.com> (raw)
Hello!
This series contains documentation updates, including some updates to
docbook header comments:
1. Design documentation illustrating RCU's grace-period memory
ordering guarantees.
2. Add verbiage stating that long-running irq handlers can stall
RCU grace periods.
3. Add verbiage stating that slow systems can stall RCU grace periods.
4. Update description of RCU CPU stall warning messages.
5. Replace uses of "transitive" in memory-barriers.txt.
6. Rework multicopy-atomicity section of memory-barriers.txt,
courtesy of Alan Stern.
7. Fix RCU's docbook options.
8. Add parameters to rcupdate.h docbook comments.
9. Remove extra docbook comment in rculist.h.
10. Fix docbook comments for rcu_sync functions.
11. Fix list and emphasis in rcupdate.h docbook comments.
12. Flag code segment in rcu_pointer_handoff()'s docbook comment.
13. Fix code display in rcu_pointer_handoff()'s docbook comment.
14. Fix tree.c bulleted lists in docbook comments.
15. Fix typo in pairing example in memory-barriers.txt, courtesy
of Scott Tsai.
16. Rewrite confusing statement about memory barriers in
memory-barriers.txt, courtesy of Guilherme G. Piccoli.
Thanx, Paul
------------------------------------------------------------------------
Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Diagram.html | 9
Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.html | 707 +
Documentation/RCU/Design/Memory-Ordering/TreeRCU-callback-invocation.svg | 486
Documentation/RCU/Design/Memory-Ordering/TreeRCU-callback-registry.svg | 655 +
Documentation/RCU/Design/Memory-Ordering/TreeRCU-dyntick.svg | 700 +
Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-cleanup.svg | 1126 ++
Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-fqs.svg | 1309 ++
Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-1.svg | 656 +
Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-2.svg | 656 +
Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp-init-3.svg | 632 +
Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg | 5135 ++++++++++
Documentation/RCU/Design/Memory-Ordering/TreeRCU-hotplug.svg | 775 +
Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg | 1095 ++
Documentation/RCU/Design/Memory-Ordering/rcu_node-lock.svg | 229
Documentation/RCU/stallwarn.txt | 200
Documentation/core-api/kernel-api.rst | 14
Documentation/memory-barriers.txt | 249
include/linux/rculist.h | 2
include/linux/rcupdate.h | 26
kernel/rcu/sync.c | 9
kernel/rcu/tree.c | 18
21 files changed, 14449 insertions(+), 239 deletions(-)
next reply other threads:[~2017-10-04 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 21:20 Paul E. McKenney [this message]
2017-10-04 21:21 ` [PATCH tip/core/rcu 01/16] documentation: RCU grace-period memory ordering guarantees Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 02/16] documentation: Long-running irq handlers can stall RCU grace periods Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 03/16] documentation: Slow systems " Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 04/16] documentation: Update RCU CPU stall warning messages Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 05/16] memory-barriers: Replace uses of "transitive" Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 06/16] memory-barriers: Rework multicopy-atomicity section Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 07/16] doc: Fix options for RCU options Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 08/16] doc: Add parameters to rcupdate.h docbook comments Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 09/16] rcu: Remove extra docbook comment in rculist.h Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 10/16] rcu: Fix docbook comments for rcu_sync functions Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 11/16] doc: Fix list and emphasis in rcupdate.h Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 12/16] doc: Flag code segment in rcu_pointer_handoff()'s docbook header Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 13/16] doc: Fix code display in rcu_pointer_handoff()'s docbook comment Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 14/16] doc: Fix tree.c bulleted lists in docbook comment headers Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 15/16] memory-barriers.txt: Fix typo in pairing example Paul E. McKenney
2017-10-04 21:21 ` [PATCH tip/core/rcu 16/16] Documentation: rewrite confusing statement about memory barriers 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=20171004212051.GA8411@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox