public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Florent Carli via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Florent Carli <fcarli@gmail.com>
Subject: [pve-devel] Plans for Realtime Kernel and Realtime Configuration Support in Proxmox?
Date: Fri, 16 May 2025 10:02:21 +0200	[thread overview]
Message-ID: <mailman.501.1747737475.394.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 5969 bytes --]

From: Florent Carli <fcarli@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: Plans for Realtime Kernel and Realtime Configuration Support in Proxmox?
Date: Fri, 16 May 2025 10:02:21 +0200
Message-ID: <CAJuRqcAk8xtaXW9kRod6eq3TFteKW0_Kx8tBVA0h40hRV1S+Xg@mail.gmail.com>

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).
- 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...

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?

Thanks in advance, and looking forward to your thoughts!

Best regards,
Florent


[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

             reply	other threads:[~2025-05-20 10:38 UTC|newest]

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

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=mailman.501.1747737475.394.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=fcarli@gmail.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