All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mike Galbraith <efault@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Paul Turner <pjt@google.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Clark Williams <clark@redhat.com>,
	Andrew Theurer <habanero@us.ibm.com>
Subject: Re: [RFC] sched: The removal of idle_balance()
Date: Sun, 17 Feb 2013 16:54:49 -0500	[thread overview]
Message-ID: <1361138089.23152.141.camel@gandalf.local.home> (raw)
In-Reply-To: <1361085245.28353.3.camel@marge.simpson.net>

On Sun, 2013-02-17 at 08:14 +0100, Mike Galbraith wrote:

> (And puts a dent in x264 ultrafast)
> 
> +SD_BALANCE_NEWIDLE
> encoded 600 frames, 425.04 fps, 22132.71 kb/s
> encoded 600 frames, 416.07 fps, 22132.71 kb/s
> encoded 600 frames, 417.49 fps, 22132.71 kb/s
> encoded 600 frames, 420.65 fps, 22132.71 kb/s
> encoded 600 frames, 425.55 fps, 22132.71 kb/s
> encoded 600 frames, 425.58 fps, 22132.71 kb/s
> encoded 600 frames, 426.18 fps, 22132.71 kb/s
> encoded 600 frames, 424.21 fps, 22132.71 kb/s
> encoded 600 frames, 422.20 fps, 22132.71 kb/s
> encoded 600 frames, 423.15 fps, 22132.71 kb/s
> 
> -SD_BALANCE_NEWIDLE
> encoded 600 frames, 378.52 fps, 22132.71 kb/s
> encoded 600 frames, 378.75 fps, 22132.71 kb/s
> encoded 600 frames, 378.20 fps, 22132.71 kb/s
> encoded 600 frames, 372.54 fps, 22132.71 kb/s
> encoded 600 frames, 366.69 fps, 22132.71 kb/s
> encoded 600 frames, 378.46 fps, 22132.71 kb/s
> encoded 600 frames, 379.89 fps, 22132.71 kb/s
> encoded 600 frames, 382.25 fps, 22132.71 kb/s
> encoded 600 frames, 384.10 fps, 22132.71 kb/s
> encoded 600 frames, 375.24 fps, 22132.71 kb/s

What about my last patch? The one that avoids idle_balance() if the
previous task was in a task_uninterruptible state. That one gave the
same performance increase that removing idle_balance() did on my box.

-- Steve




  reply	other threads:[~2013-02-17 21:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15  6:13 [RFC] sched: The removal of idle_balance() Steven Rostedt
2013-02-15  7:26 ` Mike Galbraith
2013-02-15 12:07   ` Peter Zijlstra
2013-02-15 12:21   ` Peter Zijlstra
2013-02-15 12:32     ` Mike Galbraith
2013-02-16 16:12   ` Steven Rostedt
2013-02-17  6:26     ` Mike Galbraith
2013-02-17  7:14       ` Mike Galbraith
2013-02-17 21:54         ` Steven Rostedt [this message]
2013-02-18  3:42           ` Mike Galbraith
2013-02-18 15:23             ` Steven Rostedt
2013-02-18 17:22               ` Mike Galbraith
2013-02-15  7:45 ` Joonsoo Kim
2013-02-15 15:05   ` Steven Rostedt
2013-02-17  6:26 ` Mike Galbraith
2013-02-18  8:13 ` Srikar Dronamraju
2013-02-18 15:25   ` Steven Rostedt
2013-02-19  4:13     ` Rakib Mullick
2013-02-19  7:29       ` Michael Wang

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=1361138089.23152.141.camel@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=acme@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=clark@redhat.com \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=habanero@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --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 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.