From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.de>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Schneider <valentin.schneider@arm.com>,
Qais Yousef <qais.yousef@arm.com>, Phil Auld <pauld@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
Quentin Perret <qperret@google.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Luca Abeni <luca.abeni@santannapisa.it>,
Morten Rasmussen <Morten.Rasmussen@arm.com>,
Dhaval Giani <dhaval.giani@oracle.com>,
Chris Hyser <chris.hyser@oracle.com>,
Waiman Long <longman@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Mike Galbraith <efault@gmx.de>,
Davidlohr Bueso <dave@stgolabs.net>,
Ben Segall <bsegall@google.com>, Will Deacon <will@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
patrick.bellasi@matbug.net,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Rik van Riel <riel@surriel.com>, Hillf Danton <hdanton@sina.com>,
Frederic Weisbecker <frederic@kernel.org>,
Viresh Kumar <vireshk@kernel.org>, Paul Turner <pjt@google.com>,
Dario Faggioli <raistlin@linux.it>,
Andi Kleen <ak@linux.intel.com>, Scott Wood <swood@redhat.com>,
Clark Williams <williams@redhat.com>,
Daniel Wagner <wagi@monom.org>, Mark Brown <broonie@kernel.org>
Subject: [ANNOUNCE] CFP: Scheduler Microconference - Linux Plumbers Conference 2021
Date: Mon, 9 Aug 2021 18:48:38 +0200 [thread overview]
Message-ID: <b325be52-7dec-4682-c0e4-43c978250dca@redhat.com> (raw)
The scheduler is an important functionality of the Linux kernel, deciding what
process gets to run when, where, and for how long. With different topologies and
workloads, it is no easy task to give the user the best experience possible.
Schedulers are one of the most discussed topics on the Linux Kernel Mailing
List, but many of these topics need further discussion in a conference format.
Indeed, the scheduler microconference is responsible for many topics to make
progress.
At last year's meet up, the Scheduler microconference achieved the following
results:
- Core scheduling was merged! [1]
- Scheduling fairness patches have been merged [2]
- Fixes to NUMA topology limitations[3]
Not only were enhancements made, but the meet-up also helped prove that some
topics were not feasible and we do not need to spend more time on them [4].
Some possible topics for this year are:
- Cgroup interface and other updates for core-scheduling [1]
- Cgroup and SCHED_DEADLINE [5]
- Capacity Awareness – For busy systems
- Interrupt Awareness
- Load Balancing:
- Wakeup [6] [7] [8]
- Periodic [6] [7]
- NUMA load balancing
If you are interested in participating in this microconference and have topics
to propose, please use the LPC CfP process, and select "Scheduler MC" for the
"Track". More topics will be added based on CfP for LPC microconference.
The submission deadline is August 31st.
Come and join us in the discussion of controlling what tasks get to run on your
machine and when. We hope to see you there!
In case of doubts, feel contact the MC Leads:
Daniel Bristot de Oliveira <bristot@redhat.com>
Dhaval Giani <dhaval.giani@oracle.com>
Chris Hyser <chris.hyser@oracle.com>
Juri Lelli <juri.lelli@redhat.com>
Vincent Guittot <vincent.guittot@linaro.org>
[1] https://lore.kernel.org/lkml/20210422120459.447350175@infradead.org/T/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=edaa5ddf3833669a25654d42c0fb653dfdd906df
[3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=620a6dc40754dc218f5b6389b5d335e9a107fd29
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=585b6d2723dc927ebc4ad884c4e879e4da8bc21f
[4] https://linuxplumbersconf.org/event/7/contributions/762/
[5] https://lore.kernel.org/lkml/cover.1610463999.git.bristot@redhat.com/
[6] https://lore.kernel.org/linux-arm-kernel/20210420001844.9116-5-song.bao.hua@hisilicon.com/T/
[7] https://www.spinics.net/lists/kernel/msg3894298.html
[8] https://www.spinics.net/lists/kernel/msg3914884.html
reply other threads:[~2021-08-09 16:48 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=b325be52-7dec-4682-c0e4-43c978250dca@redhat.com \
--to=bristot@redhat.com \
--cc=Morten.Rasmussen@arm.com \
--cc=ak@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=broonie@kernel.org \
--cc=bsegall@google.com \
--cc=chris.hyser@oracle.com \
--cc=daniel.lezcano@linaro.org \
--cc=dave@stgolabs.net \
--cc=dhaval.giani@oracle.com \
--cc=dietmar.eggemann@arm.com \
--cc=efault@gmx.de \
--cc=frederic@kernel.org \
--cc=hdanton@sina.com \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=luca.abeni@santannapisa.it \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@matbug.net \
--cc=pauld@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=qais.yousef@arm.com \
--cc=qperret@google.com \
--cc=raistlin@linux.it \
--cc=riel@surriel.com \
--cc=rostedt@goodmis.org \
--cc=swood@redhat.com \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=vireshk@kernel.org \
--cc=wagi@monom.org \
--cc=will@kernel.org \
--cc=williams@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
all inboxes | Powered by JetHome®