Hello This is a gentle reminder about RT and SCHED MC. We will have to send the schedule on the next weeks. Please, submit your topic ASAP. Thanks! On 6/20/23 19:13, Daniel Bristot de Oliveira wrote: > The real-time and scheduling micro-conference joins these two > intrinsically connected communities to discuss the next steps together. > > Over the past decade, many parts of PREEMPT_RT have been included > in the official Linux codebase. Examples include real-time mutexes, > high-resolution timers, lockdep, ftrace, RCU_PREEMPT, threaded interrupt > handlers, and more. The number of patches that need integration has been > significantly reduced, and the rest is mature enough to make their way > into mainline Linux. > > 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, where CPU isolation is critical. > > The following accomplishments have been made as a result of last > year’s micro-conference: > > - Progress on rtla/osnoise to support any workload [1] > - Progress on adding tracepoints for IPI [2] > - Improvements in RCU to reduce noise > - Progress on the latency-nice patch set [3] > > Ideas of topics to be discussed include (but are not limited to): > > - Improve responsiveness for CFS tasks - e.g., latency-nice patch > - The new EEVDF scheduler proposal [4] > - Impact of new topology on CFS including hybrid or heterogeneous system > - Taking into account task profile with IPCC or uclamp > - Improvements in CPU Isolation > - The status of PREEMPT_RT > - Locking improvements - e.g., proxy execution [5] > - Improvements on SCHED_DEADLINE > - Tooling for debugging scheduling and real-time > > It is fine if you have a new topic that is not on the list. > People are encouraged to submit any topic related to real-time > and scheduling. > > Please consider that the goal is to discuss open problems, preferably > with patch set submissions already in discussion on LKML. The > presentations are very short, and the main 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. > > Submissions are made via LPC submission systems, selecting *Track Real-time > and Scheduling MC* > > Please, forward this email for people interested on this subject (it not easy to > build the Cc: list for this email without forgetting important people :-))! > > [1] https://lore.kernel.org/lkml/f5cfbd37aefd419eefe9243b4d2fc38ed5753fe4.1668692096.git.bristot@xxxxxxxxxx/ > [2] https://lore.kernel.org/lkml/20230307143558.294354-1-vschneid@xxxxxxxxxx/T/ > [3] https://lore.kernel.org/lkml/20230224093454.956298-3-vincent.guittot@xxxxxxxxxx/ > [4] https://lore.kernel.org/lkml/20230328092622.062917921@xxxxxxxxxxxxx/T/ > [5] https://lore.kernel.org/lkml/20230411042511.1606592-1-jstultz@xxxxxxxxxx/ > > Thanks! > > -- Organizers: > - Daniel Bristot de Oliveira > - Juri Lelli > - Vincent Guittot > - Steven Rostedt
