Re: [RFC PATCH 06/16] arm: topology: Define TC2 sched energy and provide it to scheduler
From: Peter Zijlstra
Date: Tue Jun 03 2014 - 07:44:58 EST
On Fri, May 23, 2014 at 07:16:33PM +0100, Morten Rasmussen wrote:
> +static struct capacity_state cap_states_cluster_a7[] = {
> + /* Cluster only power */
> + { .cap = 358, .power = 2967, }, /* 350 MHz */
> + { .cap = 410, .power = 2792, }, /* 400 MHz */
> + { .cap = 512, .power = 2810, }, /* 500 MHz */
> + { .cap = 614, .power = 2815, }, /* 600 MHz */
> + { .cap = 717, .power = 2919, }, /* 700 MHz */
> + { .cap = 819, .power = 2847, }, /* 800 MHz */
> + { .cap = 922, .power = 3917, }, /* 900 MHz */
> + { .cap = 1024, .power = 4905, }, /* 1000 MHz */
> + };
> +
> +static struct capacity_state cap_states_cluster_a15[] = {
> + /* Cluster only power */
> + { .cap = 840, .power = 7920, }, /* 500 MHz */
> + { .cap = 1008, .power = 8165, }, /* 600 MHz */
> + { .cap = 1176, .power = 8172, }, /* 700 MHz */
> + { .cap = 1343, .power = 8195, }, /* 800 MHz */
> + { .cap = 1511, .power = 8265, }, /* 900 MHz */
> + { .cap = 1679, .power = 8446, }, /* 1000 MHz */
> + { .cap = 1847, .power = 11426, }, /* 1100 MHz */
> + { .cap = 2015, .power = 15200, }, /* 1200 MHz */
> + };
So how did you obtain these numbers? Did you use numbers provided by the
hardware people, or did you run a particular benchmark and record the
power usage?
Does that benchmark do some actual work (as opposed to a while(1) loop)
to keep more silicon lit up?
If you have a setup for measuring these, should we try and publish that
too so that people can run it on their platform and provide these
numbers?
Attachment:
pgprkkF_eyV5_.pgp
Description: PGP signature