The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Shrikanth Hegde <sshegde@linux.ibm.com>, <mingo@kernel.org>,
	<peterz@infradead.org>, <vincent.guittot@linaro.org>,
	<linux-kernel@vger.kernel.org>
Cc: <juri.lelli@redhat.com>, <vschneid@redhat.com>,
	<dietmar.eggemann@arm.com>, <tj@kernel.org>,
	<rostedt@goodmis.org>, <mgorman@suse.de>, <bsegall@google.com>,
	<arighi@nvidia.com>
Subject: Re: [PATCH v2 0/3] sched: Simplify ifdeffery around CONFIG_SCHED_SMT
Date: Wed, 13 May 2026 11:50:00 +0530	[thread overview]
Message-ID: <4faedf2f-5127-46d9-b813-606f9a40bb16@amd.com> (raw)
In-Reply-To: <20260512152125.308280-1-sshegde@linux.ibm.com>

Hello Shrikanth,

On 5/12/2026 8:51 PM, Shrikanth Hegde wrote:
> Semantics
> =========
> - For CONFIG_SCHED_SMT=y:
>     No functional change.
> - For CONFIG_SCHED_SMT=n:
>     - cpu_smt_mask(cpu) becomes cpumask_of(cpu), effectively making it
>       per CPU with no siblings.
>     - sched_smt_present remains defined, but never becomes active:
>     	 Since cpumask_weight(cpumask_of(cpu)) == 1
> 
> Performance impact
> ==================
> - CONFIG_SCHED_SMT=y:
>     No change in generated code.
> - CONFIG_SCHED_SMT=n:
>     - Small increase in text size (~0.01%) due to removal of compile-time
>       stubs. Most paths remain effectively dead due to static keys.
>     - Fast paths are protected using IS_ENABLED(CONFIG_SCHED_SMT).
> 
> With that, cpu_smt_mask() to be used unconditionally and reduces
> CONFIG_SCHED_SMT-specific code paths, improving readability and
> maintainability.
> 
> This leaves the remaining use of CONFIG_SCHED_SMT mainly for topology
> handling bits.

Thank you again cleaning this up! Feel free to include:

Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>

I also tested removing the "select SCHED_SMT" dependency for x86 after
guarding SDTL_INIT(..., SMT) behind CONFIG_SCHED_SMT and the system is
up fine; performance is terrible as expected :-)

-- 
Thanks and Regards,
Prateek


      parent reply	other threads:[~2026-05-13  6:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 15:21 [PATCH v2 0/3] sched: Simplify ifdeffery around CONFIG_SCHED_SMT Shrikanth Hegde
2026-05-12 15:21 ` [PATCH v2 1/3] topology: Introduce cpu_smt_mask for CONFIG_SCHED_SMT=n Shrikanth Hegde
2026-05-12 16:56   ` Phil Auld
2026-05-12 15:21 ` [PATCH v2 2/3] sched: Simplify ifdeffery around cpu_smt_mask Shrikanth Hegde
2026-05-12 16:57   ` Phil Auld
2026-05-12 15:21 ` [PATCH v2 3/3] sched/fair: Add compile time check in fastpaths for CONFIG_SCHED_SMT=n Shrikanth Hegde
2026-05-12 16:59   ` Phil Auld
2026-05-13  4:15     ` Shrikanth Hegde
2026-05-13 11:53       ` Phil Auld
2026-05-13  6:07   ` K Prateek Nayak
2026-05-13  6:16     ` Shrikanth Hegde
2026-05-13  6:39     ` Shrikanth Hegde
2026-05-13  6:57       ` K Prateek Nayak
2026-05-12 17:48 ` [PATCH v2 0/3] sched: Simplify ifdeffery around CONFIG_SCHED_SMT Valentin Schneider
2026-05-13  6:20 ` K Prateek Nayak [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=4faedf2f-5127-46d9-b813-606f9a40bb16@amd.com \
    --to=kprateek.nayak@amd.com \
    --cc=arighi@nvidia.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@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sshegde@linux.ibm.com \
    --cc=tj@kernel.org \
    --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