From: Andrea Righi <righi.andrea@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "David Vernet" <void@manifault.com>, "Tejun Heo" <tj@kernel.org>,
"Changwoo Min" <changwoo@igalia.com>,
"Giovanni Gherdovich" <ggherdovich@suse.cz>,
"Himadri Chhaya-Shailesh" <himadrispandya@gmail.com>,
"Piotr Górski" <lucjan.lucjanov@gmail.com>,
"Peter Jung" <admin@ptr1337.dev>,
"Kevin Becker" <kevin.becker@canonical.com>
Subject: [CFP] sched_ext Micro-conference at LPC 2024
Date: Fri, 7 Jun 2024 17:59:19 +0200 [thread overview]
Message-ID: <ZmMuV6f6nDrJGZAj@gpd> (raw)
sched_ext [1] is a Linux kernel feature which enables implementing
host-wide, safe kernel thread schedulers in BPF, and dynamically loading
them at runtime. sched_ext enables safe and rapid iterations of
scheduler implementations, thus radically widening the scope of
scheduling strategies that can be experimented with and deployed, even
in massive and complex production environments.
sched_ext was first sent to the upstream list as an RFC patch set [2]
back in November 2022. Since then, the project has evolved a great deal,
both technically, as well as in the significant growth of the community
of sched_ext users and contributors. The latest patch set has now
reached v6 [3].
This MC is the space for the community to discuss the developments of
sched_ext, its impact on the community, and to outline future strategies
aimed at potentially integrating this feature into the Linux kernel and
mainstream Linux distributions.
Ideas of topics to be discussed include (but are not limited to):
- Challenges and plans to facilitate the upstream merge of sched_ext
- User-space scheduling (offload part / all of the scheduling from
kernel to user-space)
- Scheduling for gaming and latency-sensitive workloads
- Scheduling & cpufreq integration
- Distro support
While we anticipate having a schedule with existing talk proposals at
the MC, we invite you to submit proposals for any topic(s) you'd like to
discuss. Time permitting, we are happy to readjust the schedule for
additional topics that are of relevance to the sched_ext community.
*We will consider the submissions until July 12th, AoE.*
This email has a list of people in Bcc, based on a list of sched_ext
authors and contributors. It is far from being complete. So, please
forward this message to the people on your team working on
scheduling-related topics.
[1] https://github.com/sched-ext/scx
[2] https://lore.kernel.org/lkml/20221130082313.3241517-1-tj@kernel.org/
[3] https://lore.kernel.org/lkml/20240501151312.635565-1-tj@kernel.org/
Thanks,
-David and Andrea
reply other threads:[~2024-06-07 15:59 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=ZmMuV6f6nDrJGZAj@gpd \
--to=righi.andrea@gmail.com \
--cc=admin@ptr1337.dev \
--cc=changwoo@igalia.com \
--cc=ggherdovich@suse.cz \
--cc=himadrispandya@gmail.com \
--cc=kevin.becker@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucjan.lucjanov@gmail.com \
--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