[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <564A6796.9090409@linux.intel.com>
Date: Mon, 16 Nov 2015 15:32:38 -0800
From: Arjan van de Ven <arjan@...ux.intel.com>
To: paulmck@...ux.vnet.ibm.com,
Jacob Pan <jacob.jun.pan@...ux.intel.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
John Stultz <john.stultz@...aro.org>,
LKML <linux-kernel@...r.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
Len Brown <len.brown@...el.com>,
Rafael Wysocki <rafael.j.wysocki@...el.com>,
Eduardo Valentin <edubezval@...il.com>,
Paul Turner <pjt@...gle.com>,
Josh Triplett <josh@...htriplett.org>
Subject: Re: [PATCH 2/4] timer: relax tick stop in idle entry
On 11/16/2015 3:28 PM, Paul E. McKenney wrote:
> Is this mostly an special-purpose embedded thing, or do you expect distros
> to be enabling this? If the former, I suggest CONFIG_RCU_NOCB_CPU_ALL,
> but if distros are doing this for general-purpose workloads, I instead
> suggest CONFIG_RCU_FAST_NO_HZ.
thermal overload happens a lot on small devices, but sadly also in big datacenters
where it is not uncommon to underprovision cooling capacity by a bit
(it's one of those "99% of the time you only need THIS much, the 1% you need 30% more"
and that more is expensive or even impractical)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists