From: Ingo Molnar <mingo@kernel.org>
To: Shrikanth Hegde <sshegde@linux.vnet.ibm.com>
Cc: mingo@redhat.com, peterz@infradead.org,
vincent.guittot@linaro.org, vschneid@redhat.com,
dietmar.eggemann@arm.com, linux-kernel@vger.kernel.org,
qperret@google.com, srikar@linux.vnet.ibm.com,
pierre.gondois@arm.com, yu.c.chen@intel.com,
tim.c.chen@linux.intel.com, pauld@redhat.com,
lukasz.luba@arm.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH v6 1/2] sched/topology: Remove EM_MAX_COMPLEXITY limit
Date: Mon, 9 Oct 2023 13:08:34 +0200 [thread overview]
Message-ID: <ZSPfMjuOC5dTkx5i@gmail.com> (raw)
In-Reply-To: <20231009060037.170765-2-sshegde@linux.vnet.ibm.com>
* Shrikanth Hegde <sshegde@linux.vnet.ibm.com> wrote:
> From: Pierre Gondois <Pierre.Gondois@arm.com>
>
> The Energy Aware Scheduler (EAS) estimates the energy consumption
> of placing a task on different CPUs. The goal is to minimize this
> energy consumption. Estimating the energy of different task placements
> is increasingly complex with the size of the platform. To avoid having
> a slow wake-up path, EAS is only enabled if this complexity is low
> enough.
...
> To reflect this improvement, remove the EAS complexity check.
> Note that a limit on the number of CPUs still holds against
> EM_MAX_NUM_CPUS to avoid overflows during the energy estimation.
>
> Signed-off-by: Pierre Gondois <Pierre.Gondois@arm.com>
> Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
> Reviewed-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
> ---
> Documentation/scheduler/sched-energy.rst | 29 ++----------------
> kernel/sched/topology.c | 39 ++----------------------
> 2 files changed, 6 insertions(+), 62 deletions(-)
I've applied this patch to tip:sched/core, for a v6.7 merge, thanks!
Ingo
next prev parent reply other threads:[~2023-10-09 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 6:00 [PATCH v6 0/2] sched: EAS changes for EM complexity and sysctl Shrikanth Hegde
2023-10-09 6:00 ` [PATCH v6 1/2] sched/topology: Remove EM_MAX_COMPLEXITY limit Shrikanth Hegde
2023-10-09 11:08 ` Ingo Molnar [this message]
2023-10-09 6:00 ` [PATCH v6 2/2] sched/topology: change behaviour of sysctl sched_energy_aware based on the platform Shrikanth Hegde
2023-10-09 14:49 ` Valentin Schneider
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=ZSPfMjuOC5dTkx5i@gmail.com \
--to=mingo@kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=qperret@google.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=sshegde@linux.vnet.ibm.com \
--cc=tim.c.chen@linux.intel.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=yu.c.chen@intel.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;
as well as URLs for NNTP newsgroup(s).