mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 5/5] powercap/drivers/dtpm: Scale the power with the load
Date: Wed, 10 Mar 2021 11:22:10 +0000	[thread overview]
Message-ID: <d2a57633-074a-f0c3-25dc-7ebdf8455d2f@arm.com> (raw)
In-Reply-To: <20210310110212.26512-5-daniel.lezcano@linaro.org>



On 3/10/21 11:02 AM, Daniel Lezcano wrote:
> Currently the power consumption is based on the current OPP power
> assuming the entire performance domain is fully loaded.
> 
> That gives very gross power estimation and we can do much better by
> using the load to scale the power consumption.
> 
> Use the utilization to normalize and scale the power usage over the
> max possible power.
> 
> Tested on a rock960 with 2 big CPUS, the power consumption estimation
> conforms with the expected one.
> 
> Before this change:
> 
> ~$ ~/dhrystone -t 1 -l 10000&
> ~$ cat /sys/devices/virtual/powercap/dtpm/dtpm:0/dtpm:0:1/constraint_0_max_power_uw
> 2260000
> 
> After this change:
> 
> ~$ ~/dhrystone -t 1 -l 10000&
> ~$ cat /sys/devices/virtual/powercap/dtpm/dtpm:0/dtpm:0:1/constraint_0_max_power_uw
> 1130000
> 
> ~$ ~/dhrystone -t 2 -l 10000&
> ~$ cat /sys/devices/virtual/powercap/dtpm/dtpm:0/dtpm:0:1/constraint_0_max_power_uw
> 2260000
> 
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
> 
> V3:
>    - Fixed uninitialized 'cpu' in scaled_power_uw()
> V2:
>    - Replaced cpumask by em_span_cpus
>    - Changed 'util' metrics variable types
>    - Optimized utilization scaling power computation
>    - Renamed parameter name for scale_pd_power_uw()
> ---
>   drivers/powercap/dtpm_cpu.c | 46 +++++++++++++++++++++++++++++++------
>   1 file changed, 39 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/powercap/dtpm_cpu.c b/drivers/powercap/dtpm_cpu.c
> index ac7f2e7e262f..47854923d958 100644
> --- a/drivers/powercap/dtpm_cpu.c
> +++ b/drivers/powercap/dtpm_cpu.c
> @@ -68,27 +68,59 @@ static u64 set_pd_power_limit(struct dtpm *dtpm, u64 power_limit)
>   	return power_limit;
>   }
>   
> +static u64 scale_pd_power_uw(struct cpumask *pd_mask, u64 power)
> +{
> +	unsigned long max = 0, sum_util = 0;
> +	int cpu;
> +
> +	for_each_cpu_and(cpu, pd_mask, cpu_online_mask) {
> +
> +		/*
> +		 * The capacity is the same for all CPUs belonging to
> +		 * the same perf domain, so a single call to
> +		 * arch_scale_cpu_capacity() is enough. However, we
> +		 * need the CPU parameter to be initialized by the
> +		 * loop, so the call ends up in this block.
> +		 *
> +		 * We can initialize 'max' with a cpumask_first() call
> +		 * before the loop but the bits computation is not
> +		 * worth given the arch_scale_cpu_capacity() just
> +		 * returns a value where the resulting assembly code
> +		 * will be optimized by the compiler.
> +		 */
> +		max = arch_scale_cpu_capacity(cpu);
> +		sum_util += sched_cpu_util(cpu, max);
> +	}
> +
> +	/*
> +	 * In the improbable case where all the CPUs of the perf
> +	 * domain are offline, 'max' will be zero and will lead to an
> +	 * illegal operation with a zero division.
> +	 */
> +	return max ? (power * ((sum_util << 10) / max)) >> 10 : 0;
> +}
> +
>   static u64 get_pd_power_uw(struct dtpm *dtpm)
>   {
>   	struct dtpm_cpu *dtpm_cpu = to_dtpm_cpu(dtpm);
>   	struct em_perf_domain *pd;
> -	struct cpumask cpus;
> +	struct cpumask *pd_mask;
>   	unsigned long freq;
> -	int i, nr_cpus;
> +	int i;
>   
>   	pd = em_cpu_get(dtpm_cpu->cpu);
> -	freq = cpufreq_quick_get(dtpm_cpu->cpu);
>   
> -	cpumask_and(&cpus, cpu_online_mask, to_cpumask(pd->cpus));
> -	nr_cpus = cpumask_weight(&cpus);
> +	pd_mask = em_span_cpus(pd);
> +
> +	freq = cpufreq_quick_get(dtpm_cpu->cpu);
>   
>   	for (i = 0; i < pd->nr_perf_states; i++) {
>   
>   		if (pd->table[i].frequency < freq)
>   			continue;
>   
> -		return pd->table[i].power *
> -			MICROWATT_PER_MILLIWATT * nr_cpus;
> +		return scale_pd_power_uw(pd_mask, pd->table[i].power *
> +					 MICROWATT_PER_MILLIWATT);
>   	}
>   
>   	return 0;
> 

LGTM

Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>

  reply	other threads:[~2021-03-10 11:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 11:02 [PATCH v3 1/5] powercap/drivers/dtpm: Encapsulate even more the code Daniel Lezcano
2021-03-10 11:02 ` [PATCH v3 2/5] powercap/drivers/dtpm: Create a registering system Daniel Lezcano
2021-03-11 10:23   ` Lukasz Luba
2021-03-10 11:02 ` [PATCH v3 3/5] powercap/drivers/dtpm: Simplify the dtpm table Daniel Lezcano
2021-03-10 11:02 ` [PATCH v3 4/5] powercap/drivers/dtpm: Use container_of instead of a private data field Daniel Lezcano
2021-03-10 11:02 ` [PATCH v3 5/5] powercap/drivers/dtpm: Scale the power with the load Daniel Lezcano
2021-03-10 11:22   ` Lukasz Luba [this message]
2021-03-11 10:15 ` [PATCH v3 1/5] powercap/drivers/dtpm: Encapsulate even more the code Lukasz Luba
2021-03-11 10:57   ` Daniel Lezcano
2021-03-12 10:11     ` Lukasz Luba
2021-03-12 10:22       ` Lukasz Luba

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=d2a57633-074a-f0c3-25dc-7ebdf8455d2f@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.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

all inboxes | Powered by JetHome®