public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	rjw@rjwysocki.net, viresh.kumar@linaro.org,
	vincent.guittot@linaro.org, qperret@google.com,
	dietmar.eggemann@arm.com, vincent.donnefort@arm.com,
	Beata.Michalska@arm.com, mingo@redhat.com, juri.lelli@redhat.com,
	rostedt@goodmis.org, segall@google.com, mgorman@suse.de,
	bristot@redhat.com, thara.gopinath@linaro.org,
	amit.kachhap@gmail.com, amitk@kernel.org, rui.zhang@intel.com,
	daniel.lezcano@linaro.org
Subject: Re: [PATCH v4 0/3] Add allowed CPU capacity knowledge to EAS
Date: Wed, 16 Jun 2021 14:33:07 +0100	[thread overview]
Message-ID: <9e8a2c92-161d-e1f3-efd9-ac0fa4d62fd5@arm.com> (raw)
In-Reply-To: <20210614185815.15136-1-lukasz.luba@arm.com>

Hi Peter,


On 6/14/21 7:58 PM, Lukasz Luba wrote:
> Hi all,
> 
> The patch set v4 aims to add knowledge about reduced CPU capacity
> into the Energy Model (EM) and Energy Aware Scheduler (EAS). Currently the
> issue is that SchedUtil CPU frequency and EM frequency are not aligned,
> when there is a CPU thermal capping. This causes an estimation error.
> This patch set provides the information about allowed CPU capacity
> into the EM (thanks to thermal pressure information). This improves the
> energy estimation. More info about this mechanism can be found in the
> patches description.
> 
> Changelog:
> v4:
> - removed local variable and improved description in patch 2/3
> - added Reviewed-by from Vincent for patch 2/3
> - added Acked-by from Viresh for patch 1/3
> v3 [3]:
> - switched to 'raw' per-cpu thermal pressure instead of thermal pressure
>    geometric series signal, since it more suited for purpose of
>    this use case: predicting SchedUtil frequency (Vincent, Dietmar)
> - added more comment in the patch 2/3 header for use case when thermal
>    capping might be applied even the CPUs are not over-utilized
>    (Dietmar)
> - added ACK tag from Rafael for SchedUtil part
> - added a fix patch for offline CPUs in cpufreq_cooling and per-cpu
>    thermal_pressure missing update
> v2 [2]:
> - clamp the returned value from effective_cpu_util() and avoid irq
>    util scaling issues (Quentin)
> v1 is available at [1]
> 
> Regards,
> Lukasz
> 
> [1] https://lore.kernel.org/linux-pm/20210602135609.10867-1-lukasz.luba@arm.com/
> [2] https://lore.kernel.org/lkml/20210604080954.13915-1-lukasz.luba@arm.com/
> [3] https://lore.kernel.org/lkml/20210610150324.22919-1-lukasz.luba@arm.com/
> 
> Lukasz Luba (3):
>    thermal: cpufreq_cooling: Update also offline CPUs per-cpu
>      thermal_pressure
>    sched/fair: Take thermal pressure into account while estimating energy
>    sched/cpufreq: Consider reduced CPU capacity in energy calculation
> 
>   drivers/thermal/cpufreq_cooling.c |  2 +-
>   include/linux/energy_model.h      | 16 +++++++++++++---
>   include/linux/sched/cpufreq.h     |  2 +-
>   kernel/sched/cpufreq_schedutil.c  |  1 +
>   kernel/sched/fair.c               | 13 +++++++++----
>   5 files changed, 25 insertions(+), 9 deletions(-)
> 

Could you take these 3 patches via your tree, please?
I'm asking you because the fair.c has most changes
(apart from energy_model.h) and the patches got
ACKs from Rafael and Viresh. The patch which touches
fair.c got Reviewed-by Vincent Guittot. I have address
all the comment, thus, IMHO it could fly now.

Please let me know if you like me to re-base on top
of some of your branches.

Regards,
Lukasz

      parent reply	other threads:[~2021-06-16 13:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 18:58 [PATCH v4 0/3] Add allowed CPU capacity knowledge to EAS Lukasz Luba
2021-06-14 19:10 ` [PATCH 1/3] thermal: cpufreq_cooling: Update also offline CPUs per-cpu thermal_pressure Lukasz Luba
2021-06-18  8:46   ` [tip: sched/core] thermal/cpufreq_cooling: Update " tip-bot2 for Lukasz Luba
2021-06-14 19:11 ` [PATCH v4 2/3] sched/fair: Take thermal pressure into account while estimating energy Lukasz Luba
2021-06-15 15:31   ` Dietmar Eggemann
2021-06-15 16:09     ` Lukasz Luba
2021-06-16 17:24       ` Dietmar Eggemann
2021-06-16 18:31         ` Lukasz Luba
2021-06-16 19:25         ` Vincent Guittot
2021-06-16 20:22           ` Lukasz Luba
2021-06-18  8:46   ` [tip: sched/core] " tip-bot2 for Lukasz Luba
2021-06-14 19:12 ` [PATCH v4 3/3] sched/cpufreq: Consider reduced CPU capacity in energy calculation Lukasz Luba
2021-06-18  8:46   ` [tip: sched/core] " tip-bot2 for Lukasz Luba
2021-06-16 13:33 ` Lukasz Luba [this message]

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=9e8a2c92-161d-e1f3-efd9-ac0fa4d62fd5@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=Beata.Michalska@arm.com \
    --cc=amit.kachhap@gmail.com \
    --cc=amitk@kernel.org \
    --cc=bristot@redhat.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=qperret@google.com \
    --cc=rjw@rjwysocki.net \
    --cc=rostedt@goodmis.org \
    --cc=rui.zhang@intel.com \
    --cc=segall@google.com \
    --cc=thara.gopinath@linaro.org \
    --cc=vincent.donnefort@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@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