From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
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, Borislav Petkov <bp@alien8.de>,
Arjan van de Ven <arjan@linux.intel.com>,
Kevin Hilman <khilman@linaro.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH documentation 2/2] kthread: Document ways of reducing OS jitter due to per-CPU kthreads
Date: Thu, 11 Apr 2013 14:00:56 -0700 [thread overview]
Message-ID: <20130411210056.GS29861@linux.vnet.ibm.com> (raw)
In-Reply-To: <51671878.9050800@infradead.org>
On Thu, Apr 11, 2013 at 01:09:28PM -0700, Randy Dunlap wrote:
> On 04/11/13 11:40, Paul E. McKenney wrote:
> > On Thu, Apr 11, 2013 at 10:18:26AM -0700, Randy Dunlap wrote:
> >> On 04/11/2013 09:05 AM, Paul E. McKenney wrote:
> >>> From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> >>>
> >>> The Linux kernel uses a number of per-CPU kthreads, any of which might
> >>> contribute to OS jitter at any time. The usual approach to normal
> >>> kthreads, namely to affinity them to a "housekeeping" CPU, does not
> >>
> >> ugh. to affine them
> >
> > How about s/affinity/bind/ instead?
>
> Yes, that's good.
>
> >>> work with these kthreads because they cannot operate correctly if moved
> >>> to some other CPU. This commit therefore lists ways of controlling OS
> >>> jitter from the Linux kernel's per-CPU kthreads.
> >>>
> >>> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> >>> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> >>> Cc: Steven Rostedt <rostedt@goodmis.org>
> >>> Cc: Borislav Petkov <bp@alien8.de>
> >>> Cc: Arjan van de Ven <arjan@linux.intel.com>
> >>> Cc: Kevin Hilman <khilman@linaro.org>
> >>> Cc: Christoph Lameter <cl@linux.com>
> >>> ---
> >>> Documentation/kernel-per-CPU-kthreads.txt | 159 ++++++++++++++++++++++++++++++
> >>> 1 file changed, 159 insertions(+)
> >>> create mode 100644 Documentation/kernel-per-CPU-kthreads.txt
> >>>
> >>> diff --git a/Documentation/kernel-per-CPU-kthreads.txt b/Documentation/kernel-per-CPU-kthreads.txt
> >>> new file mode 100644
> >>> index 0000000..495dacf
> >>> --- /dev/null
> >>> +++ b/Documentation/kernel-per-CPU-kthreads.txt
> >>> @@ -0,0 +1,159 @@
> >>> +REDUCING OS JITTER DUE TO PER-CPU KTHREADS
> >>> +
> >>> +
> >>> +Name: irq/%d-%s
> >>> +Purpose: Handle threaded interrupts.
> >>> +To reduce corresponding OS jitter, do the following:
> >>> +1. Use irq affinity to force the irq threads to execute on
> >>> + some other CPU.
> >>
> >> It would be very nice to explain here how that is done.
> >
> > Documentation/IRQ-affinity.txt
> >
> > I added a pointer to this near the beginning.
> >
>
> Good.
>
> > Thank you for your review and comments! Given my rationale above,
> > are you still comfortable with my applying your Reviewed-by?
>
> Sure. Thanks.
>
> >> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
I have added your Reviewed-by, thank you again!
Thanx, Paul
next prev parent reply other threads:[~2013-04-11 21:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 16:05 [PATCH documentation 0/2] OS-jitter documentation Paul E. McKenney
2013-04-11 16:05 ` [PATCH documentation 1/2] nohz1: Add documentation Paul E. McKenney
2013-04-11 16:05 ` [PATCH documentation 2/2] kthread: Document ways of reducing OS jitter due to per-CPU kthreads Paul E. McKenney
2013-04-11 17:18 ` Randy Dunlap
2013-04-11 18:40 ` Paul E. McKenney
2013-04-11 20:09 ` Randy Dunlap
2013-04-11 21:00 ` Paul E. McKenney [this message]
2013-04-11 16:48 ` [PATCH documentation 1/2] nohz1: Add documentation Randy Dunlap
2013-04-11 17:09 ` Paul E. McKenney
2013-04-11 17:14 ` Arjan van de Ven
2013-04-11 18:27 ` Paul E. McKenney
2013-04-11 18:43 ` Dipankar Sarma
2013-04-11 19:14 ` Paul E. McKenney
2013-04-11 18:25 ` Borislav Petkov
2013-04-11 19:13 ` Paul E. McKenney
2013-04-11 20:19 ` Borislav Petkov
2013-04-11 21:01 ` Paul E. McKenney
2013-04-12 8:05 ` Peter Zijlstra
2013-04-12 17:54 ` Paul E. McKenney
2013-04-12 17:56 ` Arjan van de Ven
2013-04-12 20:39 ` Paul E. McKenney
2013-04-15 16:00 ` Christoph Lameter
2013-04-15 16:41 ` Arjan van de Ven
2013-04-15 16:53 ` Christoph Lameter
2013-04-15 17:21 ` Arjan van de Ven
2013-04-19 21:01 ` Kevin Hilman
2013-04-19 21:47 ` Paul E. McKenney
2013-04-27 13:26 ` Frederic Weisbecker
-- strict thread matches above, loose matches on Subject: below --
2013-04-16 16:40 PATCH documentation 0/2] OS-jitter documentation Paul E. McKenney
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=20130411210056.GS29861@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=cl@linux.com \
--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=khilman@linaro.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=peterz@infradead.org \
--cc=rdunlap@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.