From: Pierre Gondois <pierre.gondois@arm.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: yu.c.chen@intel.com, dietmar.eggemann@arm.com,
linux-kernel@vger.kernel.org, nysal@linux.ibm.com,
aboorvad@linux.ibm.com, srikar@linux.vnet.ibm.com,
vschneid@redhat.com, morten.rasmussen@arm.com,
qyousef@layalina.io, mingo@kernel.org, peterz@infradead.org,
vincent.guittot@linaro.org
Subject: Re: [PATCH v2 1/2] sched/fair: Add EAS checks before updating overutilized
Date: Thu, 29 Feb 2024 10:11:09 +0100 [thread overview]
Message-ID: <26af2033-c5e0-43a1-8953-35435ffbbdd0@arm.com> (raw)
In-Reply-To: <72c2d279-90ae-4612-9b96-e579333b8088@linux.ibm.com>
Hello Shrikanth,
On 2/28/24 18:24, Shrikanth Hegde wrote:
>
>
> On 2/28/24 9:28 PM, Pierre Gondois wrote:
>
> Hi Pierre, Thanks for taking a look.
>
>> It is nice to avoid calling effective_cpu_util() through the following
>> when EAS is not enabled:
>> I think we are avoiding calling cpu_overutilized except in update_sg_lb_stats.
> I didnt want to put a EAS check in cpu_overutilized as it could be useful
> function in non-EAS cases in future. calling cpu_overutilized alone doesnt
> do any access to root_domain's overutilized field. So we are okay w.r.t to
> cache issues.
> But we will do some extra computation currently and then not use it if it
> Non-EAS case in update_sg_lb_stats
>
> Would something like this makes sense?
> @@ -9925,7 +9925,7 @@ static inline void update_sg_lb_stats(struct lb_env *env,
> if (nr_running > 1)
> *sg_status |= SG_OVERLOAD;
>
> - if (cpu_overutilized(i))
> + if (sched_energy_enabled() && cpu_overutilized(i))
> *sg_status |= SG_OVERUTILIZED;
>
Yes right. I think that what Dietmar suggested is also a good idea
which could be used instead.
>
>
>
> I didnt find how would util_fits_cpu ends up calling effective_cpu_util.
> Could you please elaborate?
Sorry I meant this path:
cpu_overutilized()
\-cpu_util_cfs()
\-cpu_util()
effective_cpu_util() is effectively not involved.
>
>> cpu_overutilized()
>> \-util_fits_cpu()
>> \- ...
>> \-effective_cpu_util()
>>
[snip]
Regards,
Pierre
next prev parent reply other threads:[~2024-02-29 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 7:16 [PATCH v2 0/2] sched/fair: Limit access to overutilized Shrikanth Hegde
2024-02-28 7:16 ` [PATCH v2 1/2] sched/fair: Add EAS checks before updating overutilized Shrikanth Hegde
2024-02-28 15:58 ` Pierre Gondois
2024-02-28 17:24 ` Shrikanth Hegde
2024-02-28 23:34 ` Dietmar Eggemann
2024-02-29 4:30 ` Shrikanth Hegde
2024-02-29 9:11 ` Pierre Gondois [this message]
2024-02-28 7:16 ` [PATCH v2 2/2] sched/fair: Use helper function to access rd->overutilized Shrikanth Hegde
2024-02-29 0:08 ` [PATCH v2 0/2] sched/fair: Limit access to overutilized Qais Yousef
2024-02-29 4:46 ` Shrikanth Hegde
2024-03-03 18:06 ` Qais Yousef
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=26af2033-c5e0-43a1-8953-35435ffbbdd0@arm.com \
--to=pierre.gondois@arm.com \
--cc=aboorvad@linux.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=nysal@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=srikar@linux.vnet.ibm.com \
--cc=sshegde@linux.ibm.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
all inboxes | Powered by JetHome®