devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
	Jean Pihet <jean.pihet@newoldbits.com>,
	linux@arm.linux.org.uk, devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
	linaro-dev@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 3/4] ARM: topology: Update cpu_power according to DT information
Date: Wed, 13 Jun 2012 14:47:46 +0200	[thread overview]
Message-ID: <1339591666.8980.26.camel@twins> (raw)
In-Reply-To: <CAP245DXEOGLe1jq2Wj0rNW5qea63UyJu2jOvwV65Y4B9LLoQtg@mail.gmail.com>

On Wed, 2012-06-13 at 18:14 +0530, Amit Kucheria wrote:
> Various discussions around power-aware scheduling have amplified the
> need for the scheduler to have some knowledge of DVFS. This would then
> require the scheduler to track 'cpu_power' ( = max power) and perhaps
> a new variable 'current_power' that is changed by the DVFS framework.

Note that capacity is in fact a better term -- not to be confused with
the capacity as currently in use within the load-balancer. Luckily
there's no way to read that an not be confused.. uhmm :-)
> 
> The first goal, though, is to make sure that the scheduler can handle
> different cpu_power values due to asymmetric cores. 

I would think the very first goal was to do a simple packing balancer
before doing silly things with asymmetric setups.. but what do I know.

  reply	other threads:[~2012-06-13 12:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 12:02 [RFC 0/4] ARM: topology: set the capacity of each cores for big.LITTLE Vincent Guittot
     [not found] ` <1339502524-10265-1-git-send-email-vincent.guittot-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-06-12 12:02   ` [RFC 1/4] ARM: topology: Add arch_scale_freq_power function Vincent Guittot
2012-06-13  8:50     ` Jean Pihet
2012-06-13  9:22       ` Vincent Guittot
2012-06-13 12:52     ` Peter Zijlstra
2012-06-13 19:27       ` Andy Whitcroft
2012-06-13 19:30         ` Joe Perches
2012-06-13 21:51         ` Peter Zijlstra
2012-06-12 12:02   ` [RFC 2/4] ARM: topology: factorize the update of sibling masks Vincent Guittot
2012-06-13 12:54     ` Peter Zijlstra
2012-06-12 12:02   ` [RFC 3/4] ARM: topology: Update cpu_power according to DT information Vincent Guittot
2012-06-13  8:59     ` Jean Pihet
2012-06-13  9:44       ` Vincent Guittot
2012-06-13 12:44         ` Amit Kucheria
2012-06-13 12:47           ` Peter Zijlstra [this message]
2012-06-13 12:50             ` Jean Pihet
2012-06-13 13:29             ` Vincent Guittot
2012-06-13 13:32               ` Peter Zijlstra
2012-06-13 14:31                 ` Vincent Guittot
2012-06-13 13:07     ` Peter Zijlstra
2012-06-13 14:54       ` Vincent Guittot
2012-06-13 16:06         ` Peter Zijlstra
2012-06-13 13:09     ` Peter Zijlstra
2012-06-13 14:42       ` Nicolas Pitre
     [not found]     ` <1339502524-10265-4-git-send-email-vincent.guittot-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-06-13 13:19       ` Peter Zijlstra
2012-06-12 12:02   ` [RFC 4/4] sched: cpu_power: enable ARCH_POWER Vincent Guittot
2012-06-13 12:50     ` Peter Zijlstra
2012-06-13 13:20       ` Vincent Guittot
2012-06-13 13:28         ` Peter Zijlstra
2012-06-13 13:50           ` Vincent Guittot

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=1339591666.8980.26.camel@twins \
    --to=peterz@infradead.org \
    --cc=amit.kucheria@linaro.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jean.pihet@newoldbits.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rob.herring@calxeda.com \
    --cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).