From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: alexs@kernel.org
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org, sshegde@linux.ibm.com
Subject: Re: [PATCH v2 3/6] sched/fair: cleanup sched_use_asym_prio
Date: Wed, 31 Jan 2024 17:13:46 -0800 [thread overview]
Message-ID: <20240201011346.GE18560@ranerica-svr.sc.intel.com> (raw)
In-Reply-To: <20240130131708.429425-3-alexs@kernel.org>
On Tue, Jan 30, 2024 at 09:17:05PM +0800, alexs@kernel.org wrote:
> From: Alex Shi <alexs@kernel.org>
>
> And simplify the one line code. No function change.
>
> Signed-off-by: Alex Shi <alexs@kernel.org>
> To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
> To: Valentin Schneider <vschneid@redhat.com>
> To: Vincent Guittot <vincent.guittot@linaro.org>
> To: Peter Zijlstra <peterz@infradead.org>
> To: Ingo Molnar <mingo@redhat.com>
> ---
> kernel/sched/fair.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 8d70417f5125..ebd659af2d78 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -9741,10 +9741,8 @@ group_type group_classify(unsigned int imbalance_pct,
> */
> static bool sched_use_asym_prio(struct sched_domain *sd, int cpu)
> {
> - if (!sched_smt_active())
> - return true;
> -
> - return sd->flags & SD_SHARE_CPUCAPACITY || is_core_idle(cpu);
> + return (!sched_smt_active()) ||
> + (sd->flags & SD_SHARE_CPUCAPACITY) || is_core_idle(cpu);
I think that compressing the two conditions into one hurts readability.
As implemented, it is clear that no further checks are required if there
is no SMT.
Also, please see my comment in patch 6/6.
next prev parent reply other threads:[~2024-02-01 1:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 13:17 [PATCH v2 1/6] sched/fair: add SD_CLUSTER in comments alexs
2024-01-30 13:17 ` [PATCH v2 2/6] sched/fair: remove unused parameters alexs
2024-01-30 13:17 ` [PATCH v2 3/6] sched/fair: cleanup sched_use_asym_prio alexs
2024-02-01 1:13 ` Ricardo Neri [this message]
2024-02-01 8:41 ` kuiliang Shi
2024-01-30 13:17 ` [PATCH v2 4/6] sched/fair: packing func sched_use_asym_prio/sched_asym_prefer alexs
2024-02-01 0:25 ` Ricardo Neri
2024-01-30 13:17 ` [PATCH v2 5/6] sched/fair: pack SD_ASYM_PACKING into sched_use_asym_prio alexs
2024-02-01 0:55 ` Ricardo Neri
2024-02-01 8:45 ` kuiliang Shi
2024-01-30 13:17 ` [PATCH v2 6/6 RFT] sched/fair: change sched asym checking condition alexs
2024-02-01 1:10 ` Ricardo Neri
2024-02-01 11:40 ` kuiliang Shi
2024-02-01 15:19 ` Shrikanth Hegde
2024-02-01 16:33 ` Ricardo Neri
2024-01-31 22:00 ` [PATCH v2 1/6] sched/fair: add SD_CLUSTER in comments Ricardo Neri
2024-02-01 8:58 ` Shrikanth Hegde
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=20240201011346.GE18560@ranerica-svr.sc.intel.com \
--to=ricardo.neri-calderon@linux.intel.com \
--cc=alexs@kernel.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
--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®