mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhang Qiao <zhangqiao22@huawei.com>
To: <sched-ext@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>, <tj@kernel.org>,
	<void@manifault.com>, <arighi@nvidia.com>, <changwoo@igalia.com>,
	<tanghui22@huawei.com>, <zhangqiao22@huawei.com>
Subject: [PATCH 0/4] sched_ext: Decompose scx_cid_init()
Date: Thu, 5 Nov 2026 14:50:09 +0800	[thread overview]
Message-ID: <20261105065013.784398-1-zhangqiao22@huawei.com> (raw)

scx_cid_init() grew into a ~230-line monolith interleaving table
allocation, the node/LLC/cluster/core topology walk, the no-topo tail
and the shard range finalization. This series decomposes it into stage
helpers sharing a file-private builder struct, in four individually
compilable steps:

  01/04 extract the no-topo tail and the table finalization
  02/04 collect the construction state in scx_cid_builder
  03/04 extract the construction of a single LLC cid range
  04/04 extract the online (node-level) walk

No behavior change: WARN checks, error paths, shard policy and
publication timing are all preserved. This is preparation for
follow-up fixes to the partial-SMT core counting in
calc_shard_layout() and the single-core shard hard-cap corner case,
which are deliberately kept out to keep this series a pure code
motion.

Based on tj/sched_ext for-7.5.

Signed-off-by: Zhang Qiao <zhangqiao22@huawei.com>

Zhang Qiao (4):
  sched_ext: Extract no-topology CID construction and table finalization
  sched_ext: Collect CID construction state in a private builder
  sched_ext: Extract construction of a single LLC CID range
  sched_ext: Extract online CID construction from scx_cid_init

 kernel/sched/ext/cid.c | 422 +++++++++++++++++++++++------------------
 1 file changed, 241 insertions(+), 181 deletions(-)


base-commit: beb427129cbdd0154cdb017a694779963e46b520
-- 
2.43.0


             reply	other threads:[~2026-11-05  6:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  6:50 Zhang Qiao [this message]
2026-11-05  6:50 ` [PATCH 1/4] sched_ext: Extract no-topology CID construction and table finalization Zhang Qiao
2026-11-05  6:50 ` [PATCH 2/4] sched_ext: Collect CID construction state in a private builder Zhang Qiao
2026-11-05  6:50 ` [PATCH 3/4] sched_ext: Extract construction of a single LLC CID range Zhang Qiao
2026-11-05  6:50 ` [PATCH 4/4] sched_ext: Extract online CID construction from scx_cid_init Zhang Qiao
2026-11-05 17:10 ` [PATCH 0/4] sched_ext: Decompose scx_cid_init() Tejun Heo

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=20261105065013.784398-1-zhangqiao22@huawei.com \
    --to=zhangqiao22@huawei.com \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sched-ext@lists.linux.dev \
    --cc=tanghui22@huawei.com \
    --cc=tj@kernel.org \
    --cc=void@manifault.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®