From: Kevin Hilman <khilman@linaro.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
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>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH documentation 1/2] nohz1: Add documentation.
Date: Fri, 19 Apr 2013 14:01:49 -0700 [thread overview]
Message-ID: <877gjyxmiq.fsf@linaro.org> (raw)
In-Reply-To: <1365696359-30958-1-git-send-email-paulmck@linux.vnet.ibm.com> (Paul E. McKenney's message of "Thu, 11 Apr 2013 09:05:58 -0700")
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com> writes:
> +KNOWN ISSUES
[...]
> +o Unless all CPUs are idle, at least one CPU must keep the
> + scheduling-clock interrupt going in order to support accurate
> + timekeeping.
At least with the implementation I'm using (Frederic's 3.9-nohz1
branch), at least one CPU is forced to stay out of dyntick-idle
*always*, even if all CPUs are idle.
IMO, this is important to list as a known issue since this will have
its own power implications when the system is mostly idle.
Otherwise, document looks great.
Reviewed-by: Kevin Hilman <khilman@linaro.org>
Kevin
next prev parent reply other threads:[~2013-04-19 21:01 UTC|newest]
Thread overview: 28+ 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
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 [this message]
2013-04-19 21:47 ` Paul E. McKenney
2013-04-27 13:26 ` Frederic Weisbecker
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=877gjyxmiq.fsf@linaro.org \
--to=khilman@linaro.org \
--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=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=paulmck@linux.vnet.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 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.