From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: kayracizmeci@gmail.com
Cc: arighi@nvidia.com, bsegall@google.com, christian.loehle@arm.com,
corbet@lwn.net, dietmar.eggemann@arm.com, juri.lelli@redhat.com,
kprateek.nayak@amd.com, leitao@debian.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
ltrager@nvidia.com, mgorman@suse.de, mingo@redhat.com,
pauld@redhat.com, peterz@infradead.org, rdunlap@infradead.org,
rostedt@goodmis.org, skhan@linuxfoundation.org,
srikar@linux.ibm.com, sshegde@linux.ibm.com,
vincent.guittot@linaro.org, vschneid@redhat.com,
vsethi@nvidia.com, will@kernel.org
Subject: Re: [PATCH 1/2] sched/fair: Honor asymmetric SMT priority in idle selection
Date: Fri, 18 Sep 2026 09:28:52 +0300 [thread overview]
Message-ID: <20260918062852.77446-1-kayracizmeci@gmail.com> (raw)
In-Reply-To: <20260917165515.17479-1-kayracizmeci@gmail.com>
> Hi Andrea,
> Hope I ain't got anything wrong, I'm a bit sick.
> The sched_smt_active() check on select_idle_smt_cpu seems to be redundant on here.
> We could remove this
> By moving the check on select_idle_smt_cpu() to goto block and
> adding one check before the select_idle_smt_cpu() on select_task_rq_fair(). And just calling
> select_idle_smt_cpu() on here.
> I also have a question, do we need select_idle_smt() call on here? If yes then why? I was really confused while reading.
> Thanks,
> Kayra :_:
After I don't know how much times of reading the same functions, I finally understand.
Because of has_idle_core is false, we search if there are any idle SMP's on
any of the cores.
I normally was going to send this alot earlier, but I fall asleep after
realizing this.
Also now, I don't think we need to remove the checks for one place. It complicates things,
when I tried.
I also booted the patch, it did not worked on me since I just have a regular SMT2.
So, that was the waited behavior.
So, here's this:
Tested-by: Kayra Cizmeci <kayracizmeci@gmail.com>
Annnddddddddddddddddddddddddddddddd....
This:
Reviewed-by: Kayra Cizmeci <kayracizmeci@gmail.com>
Thanks,
Kayra :-)
next prev parent reply other threads:[~2026-09-18 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 14:05 [PATCH v6 0/2] sched: Enable preferred SMT siblings on NVIDIA Olympus Andrea Righi
2026-09-17 14:05 ` [PATCH 1/2] sched/fair: Honor asymmetric SMT priority in idle selection Andrea Righi
2026-09-17 16:55 ` Kayra Cizmeci
2026-09-18 6:28 ` Kayra Cizmeci [this message]
2026-09-17 14:05 ` [PATCH 2/2] sched/topology: Add asymmetric SMT packing override Andrea Righi
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=20260918062852.77446-1-kayracizmeci@gmail.com \
--to=kayracizmeci@gmail.com \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=christian.loehle@arm.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=leitao@debian.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltrager@nvidia.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=srikar@linux.ibm.com \
--cc=sshegde@linux.ibm.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=vsethi@nvidia.com \
--cc=will@kernel.org \
/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®