mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Li Chen <me@linux.beauty>
To: Li Chen  <me@linux.beauty>," Thomas Gleixner
	"<tglx@linutronix.de>," Ingo Molnar "<mingo@redhat.com>,"
	Borislav Petkov "<bp@alien8.de>," Dave Hansen
	"<dave.hansen@linux.intel.com>,<x86@kernel.org>," H . Peter
	Anvin "<hpa@zytor.com>," Rafael J . Wysocki
	"<rafael.j.wysocki@intel.com>," Peter Zijlstra
	"<peterz@infradead.org>," Sohil Mehta "<sohil.mehta@intel.com>,"
	Brian Gerst "<brgerst@gmail.com>," Patryk Wlazlyn "
	<patryk.wlazlyn@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/4] x86/smpboot: tidy sched-topology and drop useless SMT level
Date: Sun,  6 Jul 2025 11:06:28 +0800	[thread overview]
Message-ID: <20250706030636.397197-1-me@linux.beauty> (raw)

From: Li Chen <chenl311@chinatelecom.cn>

This series cleans up sched-domain topology handling and
eliminates hundreds of pointless attach/destroy cycles for large
machines when SMT is not available.

Patch 1, 2, and 3 do some cleanup and refactor.

Patch 4 is a follow-up that simply skip SMT domain when
cpu_smt_num_threads <= 1, so the SMT level never gets created.

Tested on Qemu.

changelog:
v2: fix wording issue as suggested by Thomas [1]
v3: remove pointless memset and adjust PKG index accordingly, as
    suggested by Thomas [2], and refine some other wording issues.
v4: v4: Split refactor patche into three parts (as suggested by Peter [3])
    and refined patch 4 logic (as done by K. [4]).

[1]: https://lore.kernel.org/all/87msa2r018.ffs@tglx/
[2]: https://lore.kernel.org/all/875xglntx1.ffs@tglx/
[3]: https://lkml.org/lkml/2025/6/25/584
[4]: https://lore.kernel.org/lkml/1b706790-2fec-4582-a425-55eeff36c32e@amd.com/

Li Chen (4):
  smpboot: introduce SDTL() helper to tidy sched topology setup
  x86/smpboot: remove redundant CONFIG_SCHED_SMT
  x86/smpboot: moves x86_topology to static initialize and truncate
  x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled

 arch/powerpc/kernel/smp.c      | 34 ++++++++-------------
 arch/s390/kernel/topology.c    | 10 +++----
 arch/x86/kernel/smpboot.c      | 55 ++++++++++++++++------------------
 include/linux/sched/topology.h |  6 ++--
 kernel/sched/topology.c        | 16 ++++------
 5 files changed, 53 insertions(+), 68 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-07-06  3:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-06  3:06 Li Chen [this message]
2025-07-06  3:06 ` [PATCH v4 1/4] smpboot: introduce SDTL() helper to tidy sched topology setup Li Chen
2025-07-07  5:33   ` K Prateek Nayak
2025-07-11  0:24     ` Li Chen
2025-07-06  3:06 ` [PATCH v4 2/4] x86/smpboot: remove redundant CONFIG_SCHED_SMT Li Chen
2025-07-06  3:06 ` [PATCH v4 3/4] x86/smpboot: moves x86_topology to static initialize and truncate Li Chen
2025-07-06  3:06 ` [PATCH v4 4/4] x86/smpboot: avoid SMT domain attach/destroy if SMT is not enabled Li Chen
2025-07-07  5:39   ` K Prateek Nayak

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=20250706030636.397197-1-me@linux.beauty \
    --to=me@linux.beauty \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=patryk.wlazlyn@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sohil.mehta@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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®