All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: xenomai <xenomai@lists.linux.dev>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
Subject: Fwd: [CPF] Real-time Micro-conference at LPC
Date: Wed, 22 May 2024 18:05:32 +0200 (CEST)	[thread overview]
Message-ID: <843802480.134113.1716393932934.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <14c584dd-2847-40c3-a9c8-d38c38dae98a@kernel.org>

----- Weitergeleitete Mail -----
> Von: "Daniel Bristot de Oliveira" <bristot@kernel.org>
> The real-time community around Linux has been responsible for
> important changes in the kernel over the last few decades.
> Preemptive mode, high-resolution timers, threaded IRQs,
> sleeping locks, tracing, deadline scheduling and formal
> tracing analysis are integral parts of the kernel rooted
> in real-time efforts, mainly from the PREEMPT_RT patch set.
> The real-time and low-latency properties of Linux has
> enabled a series of modern use cases, like low-latency
> network communication with NFV and the use of Linux in
> safety-critical systems.
> 
> This MC is the space for the community to discuss the advances of
> Linux in real-time and low latency features. For example
> (but not limited to):
> 
> - Bits left for the PREEMPT_RT merge
> - Advances in the fully preemptive mode
> - CPU isolation (mainly about how to make it dynamic)
> - Tools for PREEMPT_RT and low latency analysis
> - Tools for detecting non-optimal usages of the PREEMPT_RT
> - Improvement on locks non-protected for priority inversion
> - General improvements for locking
> - General improvements for scheduling
> - Other RT operating systems that run in parallel
>   with Linux and the integration with Linux (e.g., Xenomai).
> - Real-time virtualization
> 
> Examples of topics that the community discussed over the
> last years that made progress in the RT MC:
> 
> - timerlat/osnoise tracers and RTLA
> - DL server for starvation avoidance
> - Proxy execution (still under discussion)
> - Tracing improvements - for example, to trace IPIs
> 
> It is important to notice that it is not _only_ about PREEMPT_RT,
> but anything related to real-time and low latency. For instance,
> CPU isolation, real-time scheduling, timers, other OSs that
> run in parallel... and so on.
> 
> Join us to discuss the future of real-time and low-latency Linux.
> 
> 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 the organization: Sebastian Andrzej Siewior, Frederic
> Weisbecker, Steven Rostedt, Juri Lelli and myself.

           reply	other threads:[~2024-05-22 16:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <14c584dd-2847-40c3-a9c8-d38c38dae98a@kernel.org>]

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=843802480.134113.1716393932934.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=bristot@kernel.org \
    --cc=xenomai@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.