From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@kernel.org, peterz@infradead.org, yu.c.chen@intel.com,
dietmar.eggemann@arm.com, linux-kernel@vger.kernel.org,
nysal@linux.ibm.com, aboorvad@linux.ibm.com,
srikar@linux.ibm.com, vschneid@redhat.com,
pierre.gondois@arm.com, morten.rasmussen@arm.com,
qyousef@layalina.io
Subject: Re: [PATCH v4 2/2] sched/fair: Use helper function to access rd->overutilized
Date: Tue, 5 Mar 2024 20:33:14 +0530 [thread overview]
Message-ID: <251f9b0d-3e00-4ca7-829b-e622fc0b4c49@linux.ibm.com> (raw)
In-Reply-To: <CAKfTPtCzHf_R4SwR29FsnxXTv2J4Xrmh3gfoHcVPu3KU5OLDcQ@mail.gmail.com>
On 3/5/24 7:35 PM, Vincent Guittot wrote:
> On Fri, 1 Mar 2024 at 16:18, Shrikanth Hegde <sshegde@linux.ibm.com> wrote:
>
>
> It seems that is_rd_overutilized() is always used with
> sched_energy_enabled() in the pattern:
>
> If (sched_energy_enabled() && !is_rd_overutilized(rd))
> do something
>
> This pattern includes feec() case where we have in select_task_rq_fair():
>
> If (sched_energy_enabled())
> feec():
> |-> if (is_rd_overutilized())
> |-> goto unlock
>
> which could be changed into
> If (sched_energy_enabled() && !is_rd_overutilized(rd))
> feec()
>
> Then you can create the function is_rd_not_overutilized() instead of
> is_rd_overutilized()
>
> -static inline int is_rd_overutilized(struct root_domain *rd)
> +static inline int is_rd_not_overutilized(struct root_domain *rd)
> {
> - return READ_ONCE(rd->overutilized);
> + return sched_energy_enabled() && READ_ONCE(rd->overutilized);
> }
>
> and use is_rd_not_overutilized() instead
>
Ok. Makes sense. I will keep this patch as is. and use the above
approach in a new patch.
>> +
>> static inline void set_rd_overutilized_status(struct root_domain *rd,
>> unsigned int status)
>> {
>> @@ -6686,13 +6695,14 @@ static inline void check_update_overutilized_status(struct rq *rq)
>> if (!sched_energy_enabled())
>> return;
>>
>> - if (!READ_ONCE(rq->rd->overutilized) && cpu_overutilized(rq->cpu))
>> + if (!is_rd_overutilized(rq->rd) && cpu_overutilized(rq->cpu))
>> set_rd_overutilized_status(rq->rd, SG_OVERUTILIZED);
>> }
>> #else
>> static inline void check_update_overutilized_status(struct rq *rq) { }
>> static inline void set_rd_overutilized_status(struct root_domain *rd,
>> unsigned int status) { }
>> +static inline int is_rd_overutilized(struct root_domain *rd) { }
>
> It should be
> static inline int is_rd_overutilized(struct root_domain *rd) { return 0; }
ok.
>
>> #endif
>>
>> /* Runqueue only has SCHED_IDLE tasks enqueued */
>> @@ -7974,7 +7984,7 @@ static int find_energy_efficient_cpu(struct task_struct *p, int prev_cpu)
>>
>> rcu_read_lock();
>>
prev parent reply other threads:[~2024-03-05 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 15:17 [PATCH v4 0/2] sched/fair: Limit access to overutilized Shrikanth Hegde
2024-03-01 15:17 ` [PATCH v4 1/2] sched/fair: Add EAS checks before updating overutilized Shrikanth Hegde
2024-03-03 18:50 ` Qais Yousef
2024-03-04 8:24 ` Shrikanth Hegde
2024-03-05 10:23 ` Qais Yousef
2024-03-05 14:56 ` Shrikanth Hegde
2024-03-01 15:17 ` [PATCH v4 2/2] sched/fair: Use helper function to access rd->overutilized Shrikanth Hegde
2024-03-03 18:54 ` Qais Yousef
2024-03-04 8:28 ` Shrikanth Hegde
2024-03-05 10:19 ` Qais Yousef
2024-03-05 14:05 ` Vincent Guittot
2024-03-05 15:03 ` Shrikanth Hegde [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=251f9b0d-3e00-4ca7-829b-e622fc0b4c49@linux.ibm.com \
--to=sshegde@linux.ibm.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=pierre.gondois@arm.com \
--cc=qyousef@layalina.io \
--cc=srikar@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®