From: Andrea Righi <arighi@nvidia.com>
To: Changwoo Min <changwoo@igalia.com>
Cc: Emil Tsalapatis <emil@etsalapatis.com>,
sched-ext@lists.linux.dev, tj@kernel.org, void@manifault.com
Subject: Re: [PATCH 0/4] tools/sched_ext: Add example C schedulers
Date: Tue, 13 Jan 2026 07:33:49 +0100 [thread overview]
Message-ID: <aWXnTUC1kXitcpTw@gpd4> (raw)
In-Reply-To: <77b165ff-0cc4-44bd-b3ef-9221f8238f20@igalia.com>
On Tue, Jan 13, 2026 at 02:57:13PM +0900, Changwoo Min wrote:
> Hi Emil,
>
> On 1/13/26 6:41 AM, Emil Tsalapatis wrote:
> > Add to the tree several C sched-ext schedulers developed and maintained
> > out-of-tree by the sched-ext project over the years. These schedulers
> > demonstrate sched-ext's feature set and provide a starting point for
> > scheduler development. Place the schedulers together with the existing
> > examples in tools/sched_ext.
>
> In general, I am okay to include more examples of C schedulers in the
> kernel tree. However, I am doubtful whether it is worth including the
> nest scheduler, as it has been barely maintained in recent times.
+1 on that, even if it's a good example, it's still unmaintained code.
Maybe we should just move it in a separate github repo.
For the rest of the schedulers I'm ok to include them in-tree (still under
the assumption that they should be considered examples).
Thanks,
-Andrea
>
> Regards,
> Changwoo Min
>
> >
> > Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
> >
> > Emil Tsalapatis (4):
> > tools/sched_ext: add scx_nest scheduler
> > tools/sched_ext: add scx_userland scheduler
> > tools/sched_ext: add scx_pair scheduler
> > tools/sched_ext: add arena based scheduler
> >
> > tools/sched_ext/Makefile | 2 +-
> > tools/sched_ext/scx_nest.bpf.c | 652 +++++++++++++++++++++++
> > tools/sched_ext/scx_nest.c | 240 +++++++++
> > tools/sched_ext/scx_nest.h | 18 +
> > tools/sched_ext/scx_nest_stats_table.h | 20 +
> > tools/sched_ext/scx_pair.bpf.c | 610 +++++++++++++++++++++
> > tools/sched_ext/scx_pair.c | 180 +++++++
> > tools/sched_ext/scx_pair.h | 9 +
> > tools/sched_ext/scx_sdt.bpf.c | 710 +++++++++++++++++++++++++
> > tools/sched_ext/scx_sdt.c | 101 ++++
> > tools/sched_ext/scx_sdt.h | 113 ++++
> > tools/sched_ext/scx_userland.bpf.c | 344 ++++++++++++
> > tools/sched_ext/scx_userland.c | 437 +++++++++++++++
> > tools/sched_ext/scx_userland.h | 17 +
> > 14 files changed, 3452 insertions(+), 1 deletion(-)
> > create mode 100644 tools/sched_ext/scx_nest.bpf.c
> > create mode 100644 tools/sched_ext/scx_nest.c
> > create mode 100644 tools/sched_ext/scx_nest.h
> > create mode 100644 tools/sched_ext/scx_nest_stats_table.h
> > create mode 100644 tools/sched_ext/scx_pair.bpf.c
> > create mode 100644 tools/sched_ext/scx_pair.c
> > create mode 100644 tools/sched_ext/scx_pair.h
> > create mode 100644 tools/sched_ext/scx_sdt.bpf.c
> > create mode 100644 tools/sched_ext/scx_sdt.c
> > create mode 100644 tools/sched_ext/scx_sdt.h
> > create mode 100644 tools/sched_ext/scx_userland.bpf.c
> > create mode 100644 tools/sched_ext/scx_userland.c
> > create mode 100644 tools/sched_ext/scx_userland.h
> >
>
next prev parent reply other threads:[~2026-01-13 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 21:41 [PATCH 0/4] tools/sched_ext: Add example C schedulers Emil Tsalapatis
2026-01-12 21:41 ` [PATCH 1/4] tools/sched_ext: add scx_nest scheduler Emil Tsalapatis
2026-01-12 21:41 ` [PATCH 2/4] tools/sched_ext: add scx_userland scheduler Emil Tsalapatis
2026-01-12 21:41 ` [PATCH 3/4] tools/sched_ext: add scx_pair scheduler Emil Tsalapatis
2026-01-12 21:41 ` [PATCH 4/4] tools/sched_ext: add arena based scheduler Emil Tsalapatis
2026-01-13 5:57 ` [PATCH 0/4] tools/sched_ext: Add example C schedulers Changwoo Min
2026-01-13 6:33 ` Andrea Righi [this message]
2026-01-13 16:05 ` Emil Tsalapatis
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=aWXnTUC1kXitcpTw@gpd4 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=emil@etsalapatis.com \
--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