public inbox for linux-kernel@vger.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, laijs@cn.fujitsu.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/6] Documentation updates for 3.21^W4.1
Date: Tue, 3 Mar 2015 08:37:14 -0800	[thread overview]
Message-ID: <20150303163714.GA5427@linux.vnet.ibm.com> (raw)

Hello!

This series contains a few documentation updates:

1.	Record the fact that the rcutree.kthread_prio kernel boot parameter
	also controls the priority of the grace-period kthreads.

2.	Update the kernel-per-CPU-kthreads.txt documentation based on
	Christoph Lameter's on-demand vmstat workers commit.

3.	Update NO_HZ.txt documentation to reflect the fact that POSIX
	timers are no longer starved on adaptive-ticks CPUs.

4.	Update kernel-per-CPU-kthreads.txt documentation to reflect
	workqueue usage and nosoftlockup boot parameter.

5.	Clarify memory-barrier semantics of atomic operations.

6.	Clarify control-dependency pairing.

							Thanx, Paul

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

 b/Documentation/atomic_ops.txt              |   45 ++++++++++++++--------------
 b/Documentation/kernel-parameters.txt       |   14 +++++---
 b/Documentation/kernel-per-CPU-kthreads.txt |   34 +++++++++++++--------
 b/Documentation/memory-barriers.txt         |   42 ++++++++++++++++++--------
 b/Documentation/timers/NO_HZ.txt            |   10 +-----
 5 files changed, 85 insertions(+), 60 deletions(-)


             reply	other threads:[~2015-03-03 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03 16:37 Paul E. McKenney [this message]
2015-03-03 16:37 ` [PATCH tip/core/rcu 1/6] documentation: Update rcutree.kthread_prio for grace-period kthread use Paul E. McKenney
2015-03-03 16:37   ` [PATCH tip/core/rcu 2/6] documentation: Update based on on-demand vmstat workers Paul E. McKenney
2015-03-03 16:37   ` [PATCH tip/core/rcu 3/6] documentation: Update NO_HZ_FULL interaction with POSIX timers Paul E. McKenney
2015-03-03 16:37   ` [PATCH tip/core/rcu 4/6] documentation: Update per-CPU kthreads documentation Paul E. McKenney
2015-03-03 16:37   ` [PATCH tip/core/rcu 5/6] documentation: Clarify memory-barrier semantics of atomic operations Paul E. McKenney
2015-03-03 16:37   ` [PATCH tip/core/rcu 6/6] documentation: Clarify control-dependency pairing 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=20150303163714.GA5427@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=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --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