[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140217212625.GA4083@linux.vnet.ibm.com>
Date: Mon, 17 Feb 2014 13:26:25 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: linux-kernel@...r.kernel.org
Cc: mingo@...nel.org, laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, dhowells@...hat.com,
edumazet@...gle.com, darren@...art.com, fweisbec@...il.com,
oleg@...hat.com, sbw@....edu
Subject: [PATCH tip/core/rcu 0/6] Documentation changes for 3.15
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(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists