From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Qais Yousef <qyousef@layalina.io>
Cc: mingo@kernel.org, peterz@infradead.org,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
linux-kernel@vger.kernel.org, vschneid@redhat.com,
qperret@google.com
Subject: Re: [PATCH v2 2/2] sched/fair: Use helper functions to access rd->overload
Date: Mon, 25 Mar 2024 10:42:05 +0530 [thread overview]
Message-ID: <59224c52-1864-4920-8bac-9da308d257db@linux.ibm.com> (raw)
In-Reply-To: <20240324011620.f3mmywh44htvlb5m@airbuntu>
On 3/24/24 6:46 AM, Qais Yousef wrote:
> On 03/22/24 19:46, Shrikanth Hegde wrote:
>>
>> if (!env->sd->parent) {
>> /* update overload indicator if we are at root domain */
>> - if (READ_ONCE(env->dst_rq->rd->overload) != (sg_status & SG_OVERLOAD))
>> - WRITE_ONCE(env->dst_rq->rd->overload, sg_status & SG_OVERLOAD);
>> + if (is_rd_overloaded(env->dst_rq->rd) != (sg_status & SG_OVERLOAD))
>> + set_rd_overload_status(env->dst_rq->rd,
>> + sg_status & SG_OVERLOAD);
>
> A bit picky, but..
>
> Wouldn't it be better to encapsulate the check of whether we're writing a new
> value inside set_rd_overload_status()? Only write if it the value changed and
> all future users wouldn't care then.
>
> I think no need to wrap the line too.
>
Yes. Makes sense all the places do the check and update, can be wrapped.
I will send out v3.
>>
>> /* Update over-utilization (tipping point, U >= 0) indicator */
>> set_rd_overutilized_status(env->dst_rq->rd,
>> @@ -12344,7 +12345,7 @@ static int sched_balance_newidle(struct rq *this_rq, struct rq_flags *rf)
>> rcu_read_lock();
>> sd = rcu_dereference_check_sched_domain(this_rq->sd);
>>
>> - if (!READ_ONCE(this_rq->rd->overload) ||
>> + if (!is_rd_overloaded(this_rq->rd) ||
>> (sd && this_rq->avg_idle < sd->max_newidle_lb_cost)) {
>>
>> if (sd)
>> @@ -2518,8 +2528,8 @@ static inline void add_nr_running(struct rq *rq, unsigned count)
>>
>> #ifdef CONFIG_SMP
>> if (prev_nr < 2 && rq->nr_running >= 2) {
>> - if (!READ_ONCE(rq->rd->overload))
>> - WRITE_ONCE(rq->rd->overload, 1);
>> + if (!is_rd_overloaded(rq->rd))
>> + set_rd_overload_status(rq->rd, 1);
>
> While at it, could you write SG_OVERLOAD instead of 1?
Done.
>
> Both patches LGTM otherwise
>
> Reviewed-by: Qais Yousef <qyousef@layalina.io>
>
>
prev parent reply other threads:[~2024-03-25 5:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 14:16 [PATCH v2 0/2] sched: Minor changes for rd->overload access Shrikanth Hegde
2024-03-22 14:16 ` [PATCH v2 1/2] sched/fair: Check rd->overload value before update Shrikanth Hegde
2024-03-22 14:16 ` [PATCH v2 2/2] sched/fair: Use helper functions to access rd->overload Shrikanth Hegde
2024-03-24 1:16 ` Qais Yousef
2024-03-25 5:12 ` 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=59224c52-1864-4920-8bac-9da308d257db@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qperret@google.com \
--cc=qyousef@layalina.io \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®