From: Matt Fleming <matt@readmodwrite.com>
To: sched-ext@lists.linux.dev
Cc: kernel-team@cloudflare.com, tj@kernel.org, arighi@nvidia.com,
void@manifault.com, changwoo@igalia.com, peterz@infradead.org,
linux-kernel@vger.kernel.org
Subject: sched_ext: Partial mode priority and fallthrough to EEVDF
Date: Tue, 10 Mar 2026 14:52:13 +0000 [thread overview]
Message-ID: <20260310145213.1060649-1-matt@readmodwrite.com> (raw)
Hi,
At Cloudflare we're experimenting with inverting the priority of the
ext_sched_class and fair_sched_class to allow us to pick SCHED_EXT
tasks to run before SCHED_NORMAL. This gives us better scheduling
decisions for those SCHED_EXT tasks where we can embed business logic
into the BPF program and prevents them being starved by the larger
number of SCHED_NORMAL tasks under CPU contention. There are a couple
of reasons we took this route:
1. Our workloads are heterogeneous and complex and we can't move entire
systems to SCHED_EXT in one shot. We want to experiment with running
SCHED_EXT in partial mode as we progressively onboard more and more
services (we run multiple services on single machines).
2. There's no way today (AFAIK) to run in "full-mode" and have BPF
schedulers fallthrough to EEVDF.
In an ideal world, 2 is what we'd want to do. Is anyone else interested
in this problem or currently working on it? Is there anything coming in
the future that would make it easier for those of us slowly
transitioning to SCHED_EXT?
Thanks,
Matt
next reply other threads:[~2026-03-10 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 14:52 Matt Fleming [this message]
2026-03-10 18:27 ` sched_ext: Partial mode priority and fallthrough to EEVDF Tejun Heo
2026-03-10 18:46 ` Andrea Righi
2026-03-11 11:22 ` Matt Fleming
2026-03-11 11:10 ` Matt Fleming
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=20260310145213.1060649-1-matt@readmodwrite.com \
--to=matt@readmodwrite.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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