mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hongyan Xia <hongyan.xia2@arm.com>
To: Lukasz Luba <lukasz.luba@arm.com>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	rafael@kernel.org
Cc: dietmar.eggemann@arm.com, rui.zhang@intel.com,
	amit.kucheria@verdurent.com, amit.kachhap@gmail.com,
	daniel.lezcano@linaro.org, viresh.kumar@linaro.org,
	len.brown@intel.com, pavel@ucw.cz, mhiramat@kernel.org,
	qyousef@layalina.io, wvw@google.com, xuewen.yan94@gmail.com
Subject: Re: [PATCH v7 15/23] PM: EM: Optimize em_cpu_energy() and remove division
Date: Wed, 7 Feb 2024 11:40:03 +0000	[thread overview]
Message-ID: <8e969ccb-888d-43c8-a9a2-d46bad4bf5e8@arm.com> (raw)
In-Reply-To: <20240117095714.1524808-16-lukasz.luba@arm.com>

On 17/01/2024 09:57, Lukasz Luba wrote:
> The Energy Model (EM) can be modified at runtime which brings new
> possibilities. The em_cpu_energy() is called by the Energy Aware Scheduler
> (EAS) in its hot path. The energy calculation uses power value for
> a given performance state (ps) and the CPU busy time as percentage for that
> given frequency.
> 
> It is possible to avoid the division by 'scale_cpu' at runtime, because
> EM is updated whenever new max capacity CPU is set in the system.
> 
> Use that feature and do the needed division during the calculation of the
> coefficient 'ps->cost'. That enhanced 'ps->cost' value can be then just
> multiplied simply by utilization:
> 
> pd_nrg = ps->cost * \Sum cpu_util
> 
> to get the needed energy for whole Performance Domain (PD).
> 
> With this optimization and earlier removal of map_util_freq(), the
> em_cpu_energy() should run faster on the Big CPU by 1.43x and on the Little
> CPU by 1.69x (RockPi 4B board).
> 
> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
> ---
>   include/linux/energy_model.h | 54 ++++++++++--------------------------
>   kernel/power/energy_model.c  |  7 ++---
>   2 files changed, 17 insertions(+), 44 deletions(-)
> 
> diff --git a/include/linux/energy_model.h b/include/linux/energy_model.h
> index 689d71f6b56f..aabfc26fcd31 100644
> --- a/include/linux/energy_model.h
> +++ b/include/linux/energy_model.h
> [...]
> @@ -208,8 +206,9 @@ static int em_compute_costs(struct device *dev, struct em_perf_state *table,
>   				return -EINVAL;
>   			}
>   		} else {
> -			power_res = table[i].power;
> -			cost = div64_u64(fmax * power_res, table[i].frequency);
> +			/* increase resolution of 'cost' precision */
> +			power_res = table[i].power * 10;

NIT: Does this have to be 10, or something simple like << 3 (* 8) also 
does the job?

Although compiler these days often are clever enough to convert x * 10 
into (x << 3) + (x << 1), and this is not on the hot path anyway, so 
just a NIT.

> +			cost = power_res / table[i].performance;
>   		}
>   
>   		table[i].cost = cost;

Reviewed-by: Hongyan Xia <hongyan.xia2@arm.com>

  reply	other threads:[~2024-02-07 11:40 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17  9:56 [PATCH v7 00/23] Introduce runtime modifiable Energy Model Lukasz Luba
2024-01-17  9:56 ` [PATCH v7 01/23] PM: EM: Add missing newline for the message log Lukasz Luba
2024-01-17 11:02   ` Hongyan Xia
2024-01-17  9:56 ` [PATCH v7 02/23] PM: EM: Extend em_cpufreq_update_efficiencies() argument list Lukasz Luba
2024-01-17 11:10   ` Hongyan Xia
2024-01-17  9:56 ` [PATCH v7 03/23] PM: EM: Find first CPU active while updating OPP efficiency Lukasz Luba
2024-01-17 12:05   ` Hongyan Xia
2024-01-17  9:56 ` [PATCH v7 04/23] PM: EM: Refactor em_pd_get_efficient_state() to be more flexible Lukasz Luba
2024-01-17 12:45   ` Hongyan Xia
2024-02-06 13:53     ` Lukasz Luba
2024-01-17  9:56 ` [PATCH v7 05/23] PM: EM: Introduce em_compute_costs() Lukasz Luba
2024-01-17  9:56 ` [PATCH v7 06/23] PM: EM: Check if the get_cost() callback is present in em_compute_costs() Lukasz Luba
2024-01-17  9:56 ` [PATCH v7 07/23] PM: EM: Split the allocation and initialization of the EM table Lukasz Luba
2024-01-17  9:56 ` [PATCH v7 08/23] PM: EM: Introduce runtime modifiable table Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 09/23] PM: EM: Use runtime modified EM for CPUs energy estimation in EAS Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 10/23] PM: EM: Add functions for memory allocations for new EM tables Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 11/23] PM: EM: Introduce em_dev_update_perf_domain() for EM updates Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 12/23] PM: EM: Add em_perf_state_from_pd() to get performance states table Lukasz Luba
2024-01-29 18:13   ` Dietmar Eggemann
2024-02-06 13:55     ` Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 13/23] PM: EM: Add performance field to struct em_perf_state and optimize Lukasz Luba
2024-01-29 18:13   ` Dietmar Eggemann
2024-01-17  9:57 ` [PATCH v7 14/23] PM: EM: Support late CPUs booting and capacity adjustment Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 15/23] PM: EM: Optimize em_cpu_energy() and remove division Lukasz Luba
2024-02-07 11:40   ` Hongyan Xia [this message]
2024-01-17  9:57 ` [PATCH v7 16/23] powercap/dtpm_cpu: Use new Energy Model interface to get table Lukasz Luba
2024-01-29 18:14   ` Dietmar Eggemann
2024-01-17  9:57 ` [PATCH v7 17/23] powercap/dtpm_devfreq: " Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 18/23] drivers/thermal/cpufreq_cooling: Use new Energy Model interface Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 19/23] drivers/thermal/devfreq_cooling: " Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 20/23] PM: EM: Change debugfs configuration to use runtime EM table data Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 21/23] PM: EM: Remove old table Lukasz Luba
2024-01-17  9:57 ` [PATCH v7 22/23] PM: EM: Add em_dev_compute_costs() Lukasz Luba
2024-01-29 18:15   ` Dietmar Eggemann
2024-01-17  9:57 ` [PATCH v7 23/23] Documentation: EM: Update with runtime modification design Lukasz Luba
2024-01-29 18:16 ` [PATCH v7 00/23] Introduce runtime modifiable Energy Model Dietmar Eggemann
2024-02-06 13:54   ` Lukasz Luba
2024-02-07  9:15 ` Lukasz Luba
2024-02-07 10:31   ` Rafael J. Wysocki
2024-02-07 11:49     ` 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=8e969ccb-888d-43c8-a9a2-d46bad4bf5e8@arm.com \
    --to=hongyan.xia2@arm.com \
    --cc=amit.kachhap@gmail.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=qyousef@layalina.io \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=wvw@google.com \
    --cc=xuewen.yan94@gmail.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 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®