From: Frederic Weisbecker <fweisbec@gmail.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
dvhart@linux.intel.com, oleg@redhat.com, bobby.prani@gmail.com
Subject: Re: [PATCH RFC tip/core/rcu 2/2] Don't track sysidle state if no nohz_full= CPUs
Date: Thu, 24 Jul 2014 16:58:45 +0200 [thread overview]
Message-ID: <20140724145842.GB25788@localhost.localdomain> (raw)
In-Reply-To: <20140723162951.GA17743@linux.vnet.ibm.com>
On Wed, Jul 23, 2014 at 09:29:51AM -0700, Paul E. McKenney wrote:
> If there are no nohz_full= CPUs, then there is currently no reason to
> track sysidle state. This commit therefore short-circuits this state
> tracking if !tick_nohz_full_enabled().
>
> Note that these checks will need to be revisited if nohz_full= state
> can ever be changed at runtime.
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
next prev parent reply other threads:[~2014-07-24 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 16:28 [PATCH RFC tip/core/rcu 1/2] Eliminate redundant rcu_sysidle_state variable Paul E. McKenney
2014-07-23 16:29 ` [PATCH RFC tip/core/rcu 2/2] Don't track sysidle state if no nohz_full= CPUs Paul E. McKenney
2014-07-24 14:58 ` Frederic Weisbecker [this message]
2014-07-23 23:43 ` [PATCH RFC tip/core/rcu 1/2] Eliminate redundant rcu_sysidle_state variable Pranith Kumar
2014-07-24 14:29 ` 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=20140724145842.GB25788@localhost.localdomain \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®