public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Plans for Realtime Kernel and Realtime Configuration Support in Proxmox?
Date: Wed, 11 Jun 2025 11:33:38 +0200 (CEST)	[thread overview]
Message-ID: <1093388448.879.1749634418581@webmail.proxmox.com> (raw)
In-Reply-To: <mailman.273.1749198210.395.pve-devel@lists.proxmox.com>


> Florent Carli via pve-devel <pve-devel@lists.proxmox.com> hat am 06.06.2025 10:22 CEST geschrieben:
> Hello,
> 
> After trying the user forum first, I'm turning to you here. I did a
> quick Google search to make sure the question hadn't already been
> answered (apparently not). Now I'm reaching out to the real experts :)
> 
> I’m currently exploring Proxmox for some use cases that require
> low-latency and deterministic behavior - particularly in the context
> of real-time workloads. I’m wondering if there are any current plans
> or ongoing discussions around:
> 
> - Supporting a real-time kernel (e.g., with the PREEMPT-RT preemption model).

a lot of the RT patch set got merged in 6.12, but we currently don't plan on
shipping a separate RT-optimized set of kernel packages. the sources are there,
so evaluating your own kernel build with custom KConfig values should be fairly
straightforward.

> - Enabling and integrating real-time system configurations, such as:
> - Integrated workflows for CPU isolation, IRQ affinity, and low-latency tuning
> - vCPU pinning, and using real-time scheduling policies (e.g.,
> SCHED_FIFO, SCHED_RR)
> - Integration or support for tools like tuned to do the kernel
> configuration customization options relevant to RT
> - Integration with PTP...

better support for vCPU/iothread pinning, affinity settings and various
scheduling optimizations are planned or being worked on, but those mostly
happen in the context of perf and resource usage optimization, not RT
workloads. I do suspect a lot of that work can serve as a baseline for
doing your own optimizations.

for both kernel and user space the issue is that many optimizations that
improve RT performance can either change or hurt performance characteristics
for "regular" usage.

> Are there any official efforts or community-led initiatives in this
> direction? And if not currently on the roadmap, would this be
> something of interest to the Proxmox team or the community?

in particular for features/settings that are of interest across the board,
feel free to file enhancement requests on bugzilla.proxmox.com, ideally
with reference configs and benchmark results!

thanks


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-06-11  9:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-06  8:22 Florent Carli via pve-devel
2025-06-11  9:33 ` Fabian Grünbichler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-16  8:02 Florent Carli via pve-devel

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=1093388448.879.1749634418581@webmail.proxmox.com \
    --to=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal