From: kuiliang Shi <seakeel@gmail.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>, 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>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] sched/fair: narrow the sched_use_asym_prio checking scenario
Date: Thu, 25 Jan 2024 17:35:32 +0800 [thread overview]
Message-ID: <e5b4eb14-c8e4-4888-b555-4b959cda8efe@gmail.com> (raw)
In-Reply-To: <dd4e5498-3e21-4ac1-b65a-fd132c2a7206@linux.ibm.com>
On 1/23/24 4:47 PM, Shrikanth Hegde wrote:
>
>
> On 1/17/24 2:27 PM, alexs@kernel.org wrote:
>> From: Alex Shi <alexs@kernel.org>
>>
>> Current function doesn't match it's comments, in fact, core_idle
>> checking is only meaningful with non-SMT.
>> So make the function right.
>>
>> Signed-off-by: Alex Shi <alexs@kernel.org>
>> 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 | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index 96163ab69ae0..0a321f639c79 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -9741,8 +9741,8 @@ group_type group_classify(unsigned int imbalance_pct,
>> */
>> static bool sched_use_asym_prio(struct sched_domain *sd, int cpu)
>> {
>> - return (!sched_smt_active()) ||
>> - (sd->flags & SD_SHARE_CPUCAPACITY) || is_core_idle(cpu);
>> + return (sd->flags & SD_SHARE_CPUCAPACITY) ||
>> + (!sched_smt_active() && is_core_idle(cpu));
>> }
>
> This seems wrong. This would always return false for higher than SMT domains
> if smt is active.
>
yes, thanks for point out.
> Was this meant to be sched_smt_active() && is_core_idle(cpu)?
In theory, yes, it should like this. But I have no ASYM device to test. :(
Thanks!
Alex
>
>>
>> static inline bool _sched_asym(struct sched_domain *sd,
next prev parent reply other threads:[~2024-01-25 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 8:57 [PATCH 1/5] sched/fair: add SD_CLUSTER in comments alexs
2024-01-17 8:57 ` [PATCH 2/5] sched/fair: remove unused parameters alexs
2024-01-26 0:18 ` Ricardo Neri
2024-01-17 8:57 ` [PATCH 3/5] sched/fair: cleanup sched_use_asym_prio alexs
2024-01-17 8:57 ` [PATCH 4/5] sched/fair: add a func _sched_asym alexs
2024-01-25 21:56 ` Ricardo Neri
2024-01-26 1:57 ` kuiliang Shi
2024-01-17 8:57 ` [PATCH 5/5] sched/fair: narrow the sched_use_asym_prio checking scenario alexs
2024-01-23 8:47 ` Shrikanth Hegde
2024-01-25 9:35 ` kuiliang Shi [this message]
2024-01-26 0:06 ` Ricardo Neri
2024-01-30 13:18 ` kuiliang Shi
2024-01-26 0:04 ` Ricardo Neri
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=e5b4eb14-c8e4-4888-b555-4b959cda8efe@gmail.com \
--to=seakeel@gmail.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=mgorman@suse.de \
--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®