From: Andrea Righi <arighi@nvidia.com>
To: Tejun Heo <tj@kernel.org>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
sched-ext@lists.linux.dev, Emil Tsalapatis <emil@etsalapatis.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET sched_ext/for-7.3] sched_ext: Split sub-scheduler implementation into sub.c
Date: Wed, 1 Jul 2026 12:06:43 +0200 [thread overview]
Message-ID: <akTms0YBgtR7aXoE@gpd4> (raw)
In-Reply-To: <20260701031429.1892218-1-tj@kernel.org>
Hi Tejun,
On Tue, Jun 30, 2026 at 05:14:25PM -1000, Tejun Heo wrote:
> Hello,
>
> The sub-scheduler implementation has grown and will keep growing. Move it
> out of ext.c into a new kernel/sched/ext/sub.c. The first three patches are
> mechanical prep (prefix file-local helpers, expose shared internals, inline
> a few trivial helpers) so the move itself stays pure code motion. No
> functional change.
Apart than the comment about scx_dispatch_sched() in PATCH 4/4, everything else
looks good to me.
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Thanks,
-Andrea
>
> Based on sched_ext/for-7.3 (5df6a4506d06) with sched_ext/for-7.2-fixes
> (b7d9c359e5cf) assumed merged.
>
> Tejun Heo (4):
> sched_ext: Prefix file-local ext.c helpers exposed by the sub.c split
> sched_ext: Expose the ext.c internals used by the sub.c split
> sched_ext: Inline small ext.c helpers shared across the sub.c split
> sched_ext: Split sub-scheduler implementation into sub.c
>
> kernel/sched/build_policy.c | 2 +
> kernel/sched/ext/ext.c | 1002 +++++--------------------------------------
> kernel/sched/ext/internal.h | 136 +++++-
> kernel/sched/ext/sub.c | 668 +++++++++++++++++++++++++++++
> kernel/sched/ext/sub.h | 51 +++
> 5 files changed, 973 insertions(+), 886 deletions(-)
>
> Thanks.
>
> --
> tejun
prev parent reply other threads:[~2026-07-01 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 3:14 [PATCHSET sched_ext/for-7.3] sched_ext: Split sub-scheduler implementation into sub.c Tejun Heo
2026-07-01 3:14 ` [PATCH sched_ext/for-7.3 1/4] sched_ext: Prefix file-local ext.c helpers exposed by the sub.c split Tejun Heo
2026-07-01 3:14 ` [PATCH sched_ext/for-7.3 2/4] sched_ext: Expose the ext.c internals used " Tejun Heo
2026-07-01 3:14 ` [PATCH sched_ext/for-7.3 3/4] sched_ext: Inline small ext.c helpers shared across " Tejun Heo
2026-07-01 3:14 ` [PATCH sched_ext/for-7.3 4/4] sched_ext: Split sub-scheduler implementation into sub.c Tejun Heo
2026-07-01 10:04 ` Andrea Righi
2026-07-01 17:34 ` Tejun Heo
2026-07-01 10:06 ` Andrea Righi [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=akTms0YBgtR7aXoE@gpd4 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=emil@etsalapatis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--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