From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, 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,
oleg@redhat.com, sbw@mit.edu
Subject: [PATCH tip/core/rcu 0/6] Documentation changes for 3.15
Date: Mon, 17 Feb 2014 13:26:25 -0800 [thread overview]
Message-ID: <20140217212625.GA4083@linux.vnet.ibm.com> (raw)
Hello!
This series provides a variety of documentation updates:
1. Update the documentation on actions to take to avoid frenetic
call_rcu() invocations from exhausting memory, including a mention
of internal-to-RCU avoidance measures.
2. Add a note to Documentation/memory-barriers.txt stating that
ACCESS_ONCE() provides cache coherence for accesses to any
single given variable.
3. Add an explicit statement that in control dependencies, the
condition must include the load in question.
4. Add WQ_SYSFS workqueues as a work-offloading option in
Documentation/kernel-per-CPU-kthreads.txt.
5. It turns out that some types of control dependencies require
memory barriers, most notably when the exact same store is
at the beginning of both the then-clause and the else-clause.
Document this.
6. Fixups to RTFP.txt
Thanx, Paul
------------------------------------------------------------------------
Documentation/memory-barriers.txt | 29 +++--
b/Documentation/RCU/RTFP.txt | 149 +++++++++++++++++++++++-----
b/Documentation/RCU/checklist.txt | 19 ++-
b/Documentation/kernel-per-CPU-kthreads.txt | 13 ++
b/Documentation/memory-barriers.txt | 17 +++
5 files changed, 189 insertions(+), 38 deletions(-)
next reply other threads:[~2014-02-17 21:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 21:26 Paul E. McKenney [this message]
2014-02-17 21:26 ` [PATCH tip/core/rcu 1/6] documentation: Document call_rcu() safety mechanisms and limitations Paul E. McKenney
2014-02-17 21:26 ` [PATCH tip/core/rcu 2/6] Documentation/memory-barriers.txt: ACCESS_ONCE() provides cache coherence Paul E. McKenney
2014-02-17 21:40 ` Josh Triplett
2014-02-17 22:52 ` Paul E. McKenney
2014-02-17 21:26 ` [PATCH tip/core/rcu 3/6] Documentation/memory-barriers.txt: Conditional must use prior load Paul E. McKenney
2014-02-17 21:26 ` [PATCH tip/core/rcu 4/6] Documentation/kernel-per-CPU-kthreads.txt: Workqueue affinity Paul E. McKenney
2014-02-17 21:26 ` [PATCH tip/core/rcu 5/6] Documentation/memory-barriers.txt: Need barriers() for some control dependencies Paul E. McKenney
2014-02-17 21:46 ` Josh Triplett
2014-02-17 22:58 ` Paul E. McKenney
2014-02-18 0:02 ` Josh Triplett
2014-02-18 0:17 ` Paul E. McKenney
2014-02-18 0:45 ` Josh Triplett
2014-02-18 1:21 ` Paul E. McKenney
2014-02-18 3:29 ` Josh Triplett
2014-02-18 4:57 ` Paul E. McKenney
2014-02-17 21:26 ` [PATCH tip/core/rcu 6/6] documentation: Fix some inconsistencies in RTFP.txt Paul E. McKenney
2014-02-17 21:39 ` [PATCH tip/core/rcu 1/6] documentation: Document call_rcu() safety mechanisms and limitations Josh Triplett
2014-02-17 22:52 ` Paul E. McKenney
2014-02-17 21:47 ` [PATCH tip/core/rcu 0/6] Documentation changes for 3.15 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=20140217212625.GA4083@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--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=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=niv@us.ibm.com \
--cc=oleg@redhat.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 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.