From: Andrea Righi <arighi@nvidia.com>
To: sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Joel Fernandes <joelagnelf@nvidia.com>,
Daniel Hodges <hodgesd@meta.com>,
Changwoo Min <changwoo@igalia.com>, Tejun Heo <tj@kernel.org>,
David Vernet <void@manifault.com>
Subject: Re: [ANNOUNCEMENT] LPC 2025 sched_ext Microconference CFP
Date: Wed, 6 Aug 2025 07:26:55 +0200 [thread overview]
Message-ID: <aJLnn4YbTiNXAnZG@gpd4> (raw)
In-Reply-To: <aH9NIL4C4JdDrOFt@gpd4>
Hi all,
On Tue, Jul 22, 2025 at 10:34:51AM +0200, Andrea Righi wrote:
> We are pleased to announce the Call for Proposals (CFP) for the sched_ext
> track at the 2025 edition of the Linux Plumbers Conference (LPC), taking
> place in Tokyo, Japan, from December 11–13, 2025:
>
> https://lpc.events/event/19/sessions/229/
Just a quick note to add that the deadline for submitting proposals for the
sched_ext microconference is September 30, 2025.
Looking forward to your submissions and a great discussion at LPC!
Best regards,
-Andrea
>
> 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):
> - Use of BPF arenas for task/CPU context sharing between kernel, BPF, and
> user space
> - Composable schedulers / scheduler libraries
> - Deadline server(s) for the SCHED_EXT class
> - Integration with other scheduling-related features (RCUs, proxy
> execution, PREEMPT_RT, etc.) and other Linux subsystems (e.g., power
> management, Rust-for-Linux, etc.)
> - Workload-optimized schedulers (GPU/AI, gaming, server, ...)
> - Tickless scheduling
> - Tools and benchmarks to analyze and understand scheduler activities
>
> Proposals can be submitted here:
>
> https://lpc.events/event/19/abstracts/
>
> 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>
> - Joel Fernandes <joelagnelf@nvidia.com>
> - Daniel Hodges <hodgesd@meta.com>
> - Changwoo Min <changwoo@igalia.com>
>
> We look forward to your proposals!
>
> -Andrea
next prev parent reply other threads:[~2025-08-06 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 8:34 [ANNOUNCEMENT] LPC 2025 sched_ext Microconference CFP Andrea Righi
2025-08-06 5:26 ` Andrea Righi [this message]
2025-12-04 13:50 ` Andrea Righi
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=aJLnn4YbTiNXAnZG@gpd4 \
--to=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=hodgesd@meta.com \
--cc=joelagnelf@nvidia.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