From: Ingo Molnar <mingo@kernel.org>
To: Shrikanth Hegde <sshegde@linux.ibm.com>
Cc: peterz@infradead.org, vincent.guittot@linaro.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, qyousef@layalina.io
Subject: Re: [PATCH v6 3/3] sched/fair: Combine EAS check with overutilized access
Date: Tue, 26 Mar 2024 08:58:28 +0100 [thread overview]
Message-ID: <ZgKAJAiAM61MLPBN@gmail.com> (raw)
In-Reply-To: <20240307085725.444486-4-sshegde@linux.ibm.com>
* Shrikanth Hegde <sshegde@linux.ibm.com> wrote:
> /*
> - * Ensure that caller can do EAS. overutilized value
> - * make sense only if EAS is enabled
> + * overutilized value make sense only if EAS is enabled
> */
> -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);
> }
While adding the sched_energy_enabled() condition looks OK, the _not prefix
This is silly: putting logical operators into functions names is far less
readable than a !fn()...
> - if (!is_rd_overutilized(rq->rd) && cpu_overutilized(rq->cpu))
> + if (is_rd_not_overutilized(rq->rd) && cpu_overutilized(rq->cpu))
Especially since we already have cpu_overutilized(). It's far more coherent
to have the same basic attribute functions and put any negation into
*actual* logical operators.
Thanks,
Ingo
next prev parent reply other threads:[~2024-03-26 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 8:57 [PATCH v6 0/3] sched/fair: Limit access to overutilized Shrikanth Hegde
2024-03-07 8:57 ` [PATCH v6 1/3] sched/fair: Add EAS checks before updating overutilized Shrikanth Hegde
2024-03-07 16:50 ` Vincent Guittot
2024-03-26 8:06 ` [tip: sched/core] sched/fair: Add EAS checks before updating root_domain::overutilized tip-bot2 for Shrikanth Hegde
2024-03-07 8:57 ` [PATCH v6 2/3] sched/fair: Use helper function to access rd->overutilized Shrikanth Hegde
2024-03-07 16:50 ` Vincent Guittot
2024-03-26 8:06 ` [tip: sched/core] sched/fair: Introduce is_rd_overutilized() helper function to access root_domain::overutilized tip-bot2 for Shrikanth Hegde
2024-03-07 8:57 ` [PATCH v6 3/3] sched/fair: Combine EAS check with overutilized access Shrikanth Hegde
2024-03-07 16:50 ` Vincent Guittot
2024-03-26 7:58 ` Ingo Molnar [this message]
2024-03-26 8:26 ` Vincent Guittot
2024-03-26 12:25 ` Shrikanth Hegde
2024-03-26 14:12 ` Vincent Guittot
2024-03-26 14:49 ` Shrikanth Hegde
2024-03-14 16:47 ` [PATCH v6 0/3] sched/fair: Limit access to overutilized 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=ZgKAJAiAM61MLPBN@gmail.com \
--to=mingo@kernel.org \
--cc=aboorvad@linux.ibm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nysal@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=pierre.gondois@arm.com \
--cc=qyousef@layalina.io \
--cc=srikar@linux.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