All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Clark Williams <williams@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Alessio Igor Bogani <abogani@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Chris Metcalf <cmetcalf@tilera.com>,
	Geoff Levand <geoff@infradead.org>,
	Gilad Ben Yossef <gilad@benyossef.com>,
	Hakan Akkan <hakanakkan@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	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: Fri, 8 Feb 2013 19:43:52 +0000	[thread overview]
Message-ID: <0000013cbb55dcfd-8b269a51-2d60-44de-a0c5-1ccf9925782f-000000@email.amazonses.com> (raw)
In-Reply-To: <20130208125747.06a1e260@riff.lan>

On Fri, 8 Feb 2013, Clark Williams wrote:

> I was a little apprehensive when you started talking about multiple
> tasks in Adaptive NOHZ mode on a core but the more I started thinking
> about it, I realized that we might end up in a cooperative multitasking
> mode with no tick at all going. Multiple SCHED_FIFO threads could
> run until blocking and another would be picked. Depends on well
> behaved threads of course, so probably many cases of users shooting off
> some toes with this...
>
> Of course if you mix scheduling policies or have RT throttling turned
> on we'll need some sort of tick for preemption. But if we can keep the
> timer reprogramming down we may see some big wins for RT and HPC loads.

We could tune the (hr)timer tick to have the same interval as the time
slice interval for a process and make that constant for all processes on a
hardware thread?


      reply	other threads:[~2013-02-08 19:43 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
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 [this message]

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=0000013cbb55dcfd-8b269a51-2d60-44de-a0c5-1ccf9925782f-000000@email.amazonses.com \
    --to=cl@linux.com \
    --cc=abogani@kernel.org \
    --cc=akpm@linux-foundation.org \
    --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=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    --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.