From: Andrea Righi <arighi@nvidia.com>
To: sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>
Subject: [ANNOUNCEMENT/CFP] LPC 2026 sched_ext Microconference
Date: Mon, 1 Jun 2026 08:41:36 +0200 [thread overview]
Message-ID: <ah0poFjR91-HFbDI@gpd4> (raw)
We are pleased to announce the Call for Proposals (CFP) for the sched_ext track
at the 2026 edition of the Linux Plumbers Conference (LPC), taking place in
Prague, Czechia, from October 5–7, 2026:
https://lpc.events/event/20/sessions/270/
This microconference provides an opportunity for the community to discuss
upcoming sched_ext development and outline future strategies for improving
integration within the Linux ecosystem.
Topics suggested for discussion include (but are not limited to):
- Hierarchical cgroup sub-schedulers
- Integration with SCHED_DEADLINE (DL server interface and related improvements)
- Proxy execution support
- Device-aware scheduling policies (e.g., GPU auto-affinitization)
- Composable schedulers and reusable scheduler libraries (leveraging BPF arenas)
- Scheduling strategies for gaming and latency-sensitive workloads
- Tickless scheduling and CPU isolation
- Improved tooling for tracing and visualizing scheduler performance
Proposals can be submitted here (select "sched_ext: The BPF extensible scheduler
class MC" as the track):
https://lpc.events/event/20/abstracts/
Please submit your proposals by July 24th 2026 to give us time to schedule talks
in advance of the conference.
Note that the primary purpose of a microconference talk is open discussion, not
formal presentations. Slides should be brief and only provide context. Each
15-30 minute topic is intended to encourage brainstorming and discuss open
issues, not necessarily to resolve them.
For any questions, feel free to contact the microconference leads:
- Andrea Righi <arighi@nvidia.com>
- Changwoo Min <changwoo@igalia.com>
We look forward to your proposals!
-Andrea
reply other threads:[~2026-06-01 6:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ah0poFjR91-HFbDI@gpd4 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.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