[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1360256627.2621.77.camel@gandalf.local.home>
Date: Thu, 07 Feb 2013 12:03:47 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Alessio Igor Bogani <abogani@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Chris Metcalf <cmetcalf@...era.com>,
Christoph Lameter <cl@...ux.com>,
Geoff Levand <geoff@...radead.org>,
Gilad Ben Yossef <gilad@...yossef.com>,
Hakan Akkan <hakanakkan@...il.com>,
Li Zhong <zhong@...ux.vnet.ibm.com>,
Namhyung Kim <namhyung.kim@....com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [ANNOUNCE] 3.8-rc6-nohz4
On Thu, 2013-02-07 at 17:45 +0100, Frederic Weisbecker wrote:
> >
> > config NO_HZ_TASK
> > bool "Stop tick on specified CPUs when single task is running"
> > default n
> > depends on NO_HZ
>
> Ok I launched another debate about that single task thing. I wish we
> don't make it a fundamental component but rather an implementation
> detail that can be dynamically dealt with in the future.
It's not just an implementation detail, as it is very visible to the
user. If they want to take advantage of a task NO_HZ they have to go
through a bit of loops to make sure only a single task is running on a
CPU. We should be broadcasting this requirement to educate the users on
exactly how they can take advantage of this feature.
> Anyway let's
> talk about that on my previous answer.
I already did ;-)
-- Steve
--
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