From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: fweisbec@gmail.com, rostedt@goodmis.org, bp@alien8.de,
arjan@linux.intel.com, khilman@linaro.org, cl@linux.com,
peterz@infradead.org, tglx@linutronix.de,
olivier.baetz@novasparks.com, rdunlap@infradead.org,
zhong@linux.vnet.ibm.com, paulus@samba.org
Subject: PATCH documentation 0/2] OS-jitter documentation
Date: Tue, 16 Apr 2013 09:40:36 -0700 [thread overview]
Message-ID: <20130416164036.GA27246@linux.vnet.ibm.com> (raw)
Hello!
This is v3 of the OS-jitter-reduction documentation.
Changes from v2 (https://lkml.org/lkml/2013/4/11/337 and
https://lkml.org/lkml/2013/4/11/338):
o Updated both patches based on review feedback.
Changes from v1 (https://lkml.org/lkml/2013/3/18/462):
o Updated the nohz1 patch based on feedback from Frederic Weisbecker,
Steven Rostedt, Borislav Petkov, Arjan van de Ven, Kevin Hilman,
and Christoph Lameter.
o Added a second file describing how to reduce OS jitter from
per-CPU kthreads. This is quite rough, but is hopefully a
good starting point.
Thanx, Paul
------------------------------------------------------------------------
b/Documentation/kernel-per-CPU-kthreads.txt | 186 ++++++++++++++++++++
b/Documentation/timers/NO_HZ.txt | 255 ++++++++++++++++++++++++++++
2 files changed, 441 insertions(+)
next reply other threads:[~2013-04-16 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 16:40 Paul E. McKenney [this message]
2013-04-16 16:41 ` [PATCH documentation 1/2] nohz_full: Add documentation Paul E. McKenney
2013-04-16 16:41 ` [PATCH documentation 2/2] kthread: Document ways of reducing OS jitter due to per-CPU kthreads Paul E. McKenney
2013-04-21 19:37 ` Borislav Petkov
2013-04-23 4:03 ` Paul E. McKenney
2013-04-25 10:23 ` Borislav Petkov
2013-04-25 15:52 ` Paul E. McKenney
2013-04-25 20:59 ` Thomas Gleixner
2013-04-25 21:23 ` 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=20130416164036.GA27246@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivier.baetz@novasparks.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=zhong@linux.vnet.ibm.com \
/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.