From: Dipankar Sarma <dipankar@in.ibm.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.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>,
Kevin Hilman <khilman@linaro.org>,
Christoph Lameter <cl@linux.com>,
arnd@arndb.de, Robin.Randhawa@arm.com,
linux-rt-users@vger.kernel.org
Subject: Re: [PATCH documentation 1/2] nohz1: Add documentation.
Date: Fri, 12 Apr 2013 00:13:13 +0530 [thread overview]
Message-ID: <20130411184313.GH22229@in.ibm.com> (raw)
In-Reply-To: <20130411182727.GM29861@linux.vnet.ibm.com>
On Thu, Apr 11, 2013 at 11:27:27AM -0700, Paul E. McKenney wrote:
> On Thu, Apr 11, 2013 at 10:14:28AM -0700, Arjan van de Ven wrote:
> > >+2. Many architectures will place dyntick-idle CPUs into deep sleep
> > >+ states, which further degrades from-idle transition latencies.
> > >+
> > I think this part should just be deleted.
> > On x86, the deeper idle states are even used with non-tickless system (the break even times are
> > quite a bit less than even 1 msec).
> > I can't imagine that ARM is worse on this, at which point the statement above is highly dubious
>
> Interesting point, and I freely admit that I don't have full knowledge
> of the energy-consumption characteristics of all the architectures that
> Linux supports. Adding a few of the ARM guys on CC for their take,
> plus linux-rt-users.
>
> If there are no objections, I will delete point 2 above as Arjan suggests.
What Arjan said will also be true for Linux on Power systems. I am not
sure "many architectures" would be the right way to characterize it.
Thanks
Dipankar
next prev parent reply other threads:[~2013-04-11 18:44 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 [this message]
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
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=20130411184313.GH22229@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=Robin.Randhawa@arm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=cl@linux.com \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.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=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox