From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, 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,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
edumazet@google.com, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu
Subject: [PATCH tip/core/rcu 0/2] Documentation changes for 3.11
Date: Mon, 20 May 2013 07:49:34 -0700 [thread overview]
Message-ID: <20130520144934.GA29947@linux.vnet.ibm.com> (raw)
Hello!
A pair of documentation changes. These are not directly related to RCU,
but if no one adopts them, I will send them up with the RCU commits. The
patches are as follows:
1. Changes to the new Documentation/timers/NO_HZ.txt documentation
based on review comments from Sedat Dilek.
2. Document ways of turning off the scheduling-clock tick even when
there is more than one runnable task on a given CPU.
3. Document ways of avoiding OS jitter form the kworker workqueue
kthreads.
Thanx, Paul
------------------------------------------------------------------------
b/Documentation/kernel-per-CPU-kthreads.txt | 47 ++++++++++++++++
b/Documentation/timers/NO_HZ.txt | 79 +++++++++++++++++++++++-----
2 files changed, 114 insertions(+), 12 deletions(-)
next reply other threads:[~2013-05-20 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 14:49 Paul E. McKenney [this message]
2013-05-20 14:50 ` [PATCH tip/core/rcu 1/2] nohz_full: Update based on Sedat Dilek review Paul E. McKenney
2013-05-20 14:50 ` [PATCH tip/core/rcu 2/2] nohz_full: Document additional restrictions Paul E. McKenney
2013-05-20 14:50 ` [PATCH tip/core/rcu 1/1] kthread: Add kworker kthreads to OS-jitter documentation Paul E. McKenney
2013-05-21 17:33 ` [PATCH tip/core/rcu 0/2] Documentation changes for 3.11 Josh Triplett
2013-05-21 21:12 ` 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=20130520144934.GA29947@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--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@elte.hu \
--cc=niv@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox