All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Alessio Igor Bogani <abogani@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Chris Metcalf <cmetcalf@tilera.com>,
	Christoph Lameter <cl@linux.com>,
	Geoff Levand <geoff@infradead.org>,
	Gilad Ben Yossef <gilad@benyossef.com>,
	Hakan Akkan <hakanakkan@gmail.com>,
	Li Zhong <zhong@linux.vnet.ibm.com>,
	Namhyung Kim <namhyung.kim@lge.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ANNOUNCE] 3.8-rc6-nohz4
Date: Thu, 07 Feb 2013 12:03:47 -0500	[thread overview]
Message-ID: <1360256627.2621.77.camel@gandalf.local.home> (raw)
In-Reply-To: <CAFTL4hy-hz=okOC7mWTwP=eh_OrL48c5hoLuXyBRFMAgquLCtw@mail.gmail.com>

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



  reply	other threads:[~2013-02-07 17:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 18:28 [ANNOUNCE] 3.8-rc6-nohz4 Frederic Weisbecker
2013-02-07  2:50 ` Steven Rostedt
2013-02-07 11:10   ` Ingo Molnar
2013-02-07 15:41     ` Christoph Lameter
2013-02-07 16:12     ` Steven Rostedt
2013-02-07 16:30       ` Paul E. McKenney
2013-02-07 17:06         ` Steven Rostedt
2013-02-07 17:37           ` Paul E. McKenney
2013-02-07 16:25     ` Frederic Weisbecker
2013-02-07 16:41       ` Steven Rostedt
2013-02-07 16:45         ` Frederic Weisbecker
2013-02-07 17:03           ` Steven Rostedt [this message]
2013-02-07 17:45             ` Frederic Weisbecker
2013-02-07 19:07       ` Ingo Molnar
2013-02-07 19:19         ` Steven Rostedt
2013-02-08 15:51         ` Frederic Weisbecker
2013-02-11  9:59           ` Ingo Molnar
2013-02-07 16:41   ` Frederic Weisbecker
2013-02-07 17:00     ` Steven Rostedt
2013-02-07 17:18       ` Frederic Weisbecker
2013-02-07 19:14         ` Christoph Lameter
2013-02-07 19:55           ` Ingo Molnar
2013-02-08  6:18           ` Mike Galbraith
2013-02-08 15:53           ` Frederic Weisbecker
2013-02-08 16:18             ` Steven Rostedt
2013-02-08 16:24               ` Christoph Lameter
2013-02-08 18:57             ` Clark Williams
2013-02-08 19:43               ` Christoph Lameter

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=1360256627.2621.77.camel@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=abogani@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=cmetcalf@tilera.com \
    --cc=fweisbec@gmail.com \
    --cc=geoff@infradead.org \
    --cc=gilad@benyossef.com \
    --cc=hakanakkan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=zhong@linux.vnet.ibm.com \
    /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.