From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
linux-pm@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mel Gorman <mgorman@suse.de>, Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Valentin Schneider <vschneid@redhat.com>,
Ben Segall <bsegall@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Frederic Weisbecker <frederic@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: [CFP] Scheduling Micro-conference at Linux Plumbers 2024
Date: Mon, 20 May 2024 22:25:00 +0200 [thread overview]
Message-ID: <59680f48-df89-431a-98b9-b1cafd3ad353@kernel.org> (raw)
The scheduler is at the core of Linux performance. With different
topologies and workloads, giving the user the best experience possible
is challenging, from low latency to high throughput and from small
power-constrained devices to HPC.
The following accomplishments have been made as a result of last
year’s micro-conference:
- Progress on proxy execution
https://lore.kernel.org/lkml/20240224001153.2584030-1-jstultz@google.com/
- Progress on system pressure
https://lore.kernel.org/lkml/170073688055.398.12687414937207369825.tip-bot2@tip-bot2/
https://lore.kernel.org/lkml/20240220145947.1107937-1-vincent.guittot@linaro.org/
- Progress in the DL server
- The EEVDF scheduler and improvements in latency
- Progress on adding tracepoints for IPI
Ideas of topics to be discussed include (but are not limited to):
- Improve responsiveness for CFS tasks
- The improvements on the EEVDF scheduler proposal
- Impact of new topology on CFS, including hybrid or heterogeneous system
- Taking into account task profile with IPCC or uclamp
- Locking improvements – e.g., proxy execution
- Improvements on SCHED_DEADLINE
- Tooling for debugging scheduling
*We will consider the submissions until July 12th, AoE.*
It is fine if you have a new topic missing from the list. People are
encouraged to submit any topic related to real-time and scheduling.
The goal is to discuss open problems, preferably with patch set
submissions already in discussion on LKML. The presentations are
concise, and the central portion of the time should be given to
the debate – thus, the importance of having an open and relevant
problem with people in the community engaged in the solution.
This email has a list of people in Bcc, based on a list of
commit authors in sched/locking/power/time. It is far from being
complete. So, please forward this message to the people on
your team working on scheduling-related topics.
-- Daniel, on behalf of the organizers: Vincent Guittot, Juri Lelli,
Steven Rostedt and myself.
reply other threads:[~2024-05-20 20:25 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=59680f48-df89-431a-98b9-b1cafd3ad353@kernel.org \
--to=bristot@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).