public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Ingo Molnar" <mingo@kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [GIT PULL, RFC] Full dynticks, CONFIG_NO_HZ_FULL feature
Date: Sun, 5 May 2013 14:25:12 -0700	[thread overview]
Message-ID: <20130505212511.GC3659@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+55aFzPHkCH7CVZ4tkaF91+=GLZAxxncTq0J9d6AKpSPqovZw@mail.gmail.com>

On Sun, May 05, 2013 at 01:33:45PM -0700, Linus Torvalds wrote:
> On Sun, May 5, 2013 at 4:03 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Please consider pulling the latest timers-nohz-for-linus git tree from:
> 
> Ok, it seems to work for me, so pulled.
> 
> However, by "work for me" I mean "doesn't actually seem to make any
> difference for me". Maybe I'm odd, but the most common situation is
> either a fairly idle machine (in which case the old NOHZ did fine) or
> a fairly over-crowded one when I'm running something sufficiently
> threaded (in which case the new NOHZ_FULL doesn't do anything either).
> 
> So I really hope the "cpu has more than one running thread" case is
> getting a lot of attention. Not for 3.10, but right now it seems to
> still result in the same old 1kHz timer interrupts..
> 
> So I haven't actually found a real load where any of this makes a
> noticeable *difference*.

The workloads where we expect the most noticeable differences are
HPC workloads with short iterations and a HPC-style barrier between
each interation on the one hand and real-time workloads on the other.
My guess is that you aren't doing too much of either.

We do have some measurements taken on an early prototype of this patchset,
which are on slides 5 and 6 of:

http://linuxplumbersconf.org/2009/slides/Josh-Triplett-painless-kernel.pdf

This is for an HPC workload with a 100-microsecond iteration time.

							Thanx, Paul


  reply	other threads:[~2013-05-05 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05 11:03 [GIT PULL, RFC] Full dynticks, CONFIG_NO_HZ_FULL feature Ingo Molnar
2013-05-05 20:33 ` Linus Torvalds
2013-05-05 21:25   ` Paul E. McKenney [this message]
2013-05-06  9:25     ` Ingo Molnar
2013-05-06 15:35       ` Paul E. McKenney
2013-05-06 19:32         ` Linus Torvalds
2013-05-07  6:43           ` Ingo Molnar
2013-05-08 18:14           ` Chris Metcalf

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=20130505212511.GC3659@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /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