All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Paul Turner <pjt@google.com>, Len Brown <len.brown@intel.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Tim Chen <tim.c.chen@linux.intel.com>,
	Andi Kleen <andi.kleen@intel.com>,
	Rafael Wysocki <rafael.j.wysocki@intel.com>
Subject: Re: [RFC PATCH 3/3] sched: introduce synchronized idle injection
Date: Thu, 5 Nov 2015 11:32:35 -0800	[thread overview]
Message-ID: <20151105113235.1b98d79c@icelake> (raw)
In-Reply-To: <20151105112732.7f600ba8@icelake>

On Thu, 5 Nov 2015 11:27:32 -0800
Jacob Pan <jacob.jun.pan@linux.intel.com> wrote:

> On Thu, 5 Nov 2015 11:09:22 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
> 
> > > Before:
> > > CPU0 ______||| ||  |___________| || || |_____
> > > CPU1 _________||| ||  |_______| || |_______
> > > 
> > > After:
> > > 
> > > CPU0 ______||| ||  |___________| || || |_____
> > > CPU1 ______||| ||  |___________| || |_______
> > > 
> > > The goal is to have overlapping idle time if the load is already
> > > balanced. The energy saving can be significant.  
> > 
> > I can see such a scheme having a fairly big impact on latency, esp.
> > with forced idleness such as this. That's not going to be popular
> > for many workloads.
> agreed, it would be for limited workload. the key is to identify such
> workloads at runtime. I am thinking to use the load average of
> the busiest CPU as reference for consolidation, will not go beyond
> that.
> For the patch I have today and if you play a game like this one
> http://www.agame.com/game/cut-the-rope
sorry, hit the wrong button before finishing the email.
and set duration to 5, and 20% idle, it does not affect user experience
much. It saves ~15% power on my BDW ultrabook. Other unbalanced
workload such as video playback don't benefit, should be avoided.

  reply	other threads:[~2015-11-05 19:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03  0:10 [RFC PATCH 0/3] CFS idle injection Jacob Pan
2015-11-03  0:10 ` [RFC PATCH 1/3] ktime: add a roundup function Jacob Pan
2015-11-03  0:10 ` [RFC PATCH 2/3] timer: relax tick stop in idle entry Jacob Pan
2015-11-03  0:10 ` [RFC PATCH 3/3] sched: introduce synchronized idle injection Jacob Pan
2015-11-03 13:31   ` Peter Zijlstra
2015-11-03 14:16     ` Jacob Pan
2015-11-03 16:45     ` Jacob Pan
2015-11-05 10:09       ` Peter Zijlstra
2015-11-05 14:22         ` Arjan van de Ven
2015-11-05 14:33           ` Peter Zijlstra
2015-11-05 14:48             ` Peter Zijlstra
2015-11-05 15:28             ` Arjan van de Ven
2015-11-05 16:52               ` Peter Zijlstra
2015-11-05 18:55                 ` Thomas Gleixner
2015-11-05 18:47               ` Thomas Gleixner
2015-11-05 15:32             ` Jacob Pan
2015-11-05 16:06               ` Arjan van de Ven
2015-11-05 19:27         ` Jacob Pan
2015-11-05 19:32           ` Jacob Pan [this message]
2015-11-05 13:59     ` Peter Zijlstra
2015-11-05 23:36       ` Jacob Pan
2015-11-06  7:45         ` Peter Zijlstra
2015-11-06 23:49           ` Jacob Pan
2015-11-10  0:19             ` Jacob Pan
2015-11-04  6:06 ` [RFC PATCH 0/3] CFS " Eduardo Valentin
2015-11-04 16:58   ` Jacob Pan
2015-11-04 17:05     ` Srinivas Pandruvada
2015-11-04 18:43       ` Eduardo Valentin
2015-11-05 10:12     ` Peter Zijlstra
2015-11-06 16:50       ` Punit Agrawal
2015-11-06 19:18         ` Jacob Pan
2015-11-09 11:56           ` Punit Agrawal
2015-11-09 14:15             ` Peter Zijlstra
2015-11-09 14:43               ` Jacob Pan
2015-11-10 10:07               ` Juri Lelli
2015-11-10 10:34                 ` Peter Zijlstra
2015-11-10 10:56                   ` Juri Lelli
2015-11-09 14:36             ` Jacob Pan
2015-11-06 18:30       ` Dietmar Eggemann
2015-11-06 19:10         ` Jacob Pan
2015-11-06 21:55           ` Dietmar Eggemann
2015-11-09 21:23             ` Jacob Pan
2015-11-09 21:45               ` Peter Zijlstra

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=20151105113235.1b98d79c@icelake \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=andi.kleen@intel.com \
    --cc=arjan@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@linux.intel.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.