From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9])
by lore.proxmox.com (Postfix) with ESMTPS id DDCC81FF15E
for <inbox@lore.proxmox.com>; Tue, 20 May 2025 12:38:06 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id B3EAB198FD;
Tue, 20 May 2025 12:37:57 +0200 (CEST)
Date: Fri, 16 May 2025 10:02:21 +0200
To: pve-devel@lists.proxmox.com
X-Mailman-Approved-At: Tue, 20 May 2025 12:37:55 +0200
MIME-Version: 1.0
Message-ID: <mailman.501.1747737475.394.pve-devel@lists.proxmox.com>
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Post: <mailto:pve-devel@lists.proxmox.com>
From: Florent Carli via pve-devel <pve-devel@lists.proxmox.com>
Precedence: list
Cc: Florent Carli <fcarli@gmail.com>
X-Mailman-Version: 2.1.29
X-BeenThere: pve-devel@lists.proxmox.com
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
Subject: [pve-devel] Plans for Realtime Kernel and Realtime Configuration
Support in Proxmox?
Content-Type: multipart/mixed; boundary="===============7674924432690684444=="
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
--===============7674924432690684444==
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <fcarli@gmail.com>
X-Original-To: pve-devel@lists.proxmox.com
Delivered-To: pve-devel@lists.proxmox.com
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by lists.proxmox.com (Postfix) with ESMTPS id 70AD6CED08
for <pve-devel@lists.proxmox.com>; Fri, 16 May 2025 10:03:10 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 4F2F280D4
for <pve-devel@lists.proxmox.com>; Fri, 16 May 2025 10:02:40 +0200 (CEST)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f])
(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
(No client certificate requested)
by firstgate.proxmox.com (Proxmox) with ESMTPS
for <pve-devel@lists.proxmox.com>; Fri, 16 May 2025 10:02:39 +0200 (CEST)
Received: by mail-qt1-x82f.google.com with SMTP id d75a77b69052e-47690a4ec97so20554011cf.2
for <pve-devel@lists.proxmox.com>; Fri, 16 May 2025 01:02:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1747382552; x=1747987352; darn=lists.proxmox.com;
h=content-transfer-encoding:cc:to:subject:message-id:date:from
:mime-version:from:to:cc:subject:date:message-id:reply-to;
bh=+Knr37CWlPk/njq3hkT+6U+fEbLf6Du3LKOj0GYM2XA=;
b=ZpVTkQQYBck2eLWyvbbA/MsrfFdHD0dqhYvJZ7kRkYjryV6gWXv9XIifuYDfA5m9ix
NfpRkB1Yvf2JqoV06UrB5EztZF764SxkhEvHPxbbqrUuj28EzNOAdVuh5NzR0eqtN0jb
zLnDF6DgORe8f5fiHNaYQ9SacRmbBYeFTMbIjJvICpTne5RZUgvX1oOJAY9EqtTI4axu
t2fsPzxLjyzcZpj1mJhwooUsH38qYptcLhj3SYzMT6zsFUioivjY7z02c51y1oHpeZzY
qBgPDyQBV1/XFjuy86kdywFIGWcSkydynSiMHpyNEtoQrYnOxPPXeZ7Hnkjt2GCqUvi5
G0Zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1747382552; x=1747987352;
h=content-transfer-encoding:cc:to:subject:message-id:date:from
:mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
:reply-to;
bh=+Knr37CWlPk/njq3hkT+6U+fEbLf6Du3LKOj0GYM2XA=;
b=drXFOPybnvOqxWKX2Rea1qsBWQNn1i4/iN4aphfqspdScI03G9/V9ApqPseS2sDf41
qfdJ8IR/e9DhyTIgRScAklR52P0IZdvuWkmFLp9ALWUwZEP0JL7E4RQreXAQBU+GwNw8
C5w9OOMvOm+wxnnbMsh2b9ZqpbP8a5teMctWHjBxID5Y+i/3hQe+HI9807pQfBaS+sDt
+6GRNUVnTtN7/aGTVP+XQrFm8a+ZkQoGC9CDGcgmFsZ949BHxooq0pZAlJmR1S4Ie97S
kdZUevcMcHsY2zG4ol6V+iL7XNxn8uVY6wBXAOA/sqMiBKqvh8kvcEY04VQb0AQNJArr
gMUA==
X-Gm-Message-State: AOJu0YwvrJSDXQMn43dscvazCSRgPD2Gm1Rc1zfeZdOrxzOOOX6rHXTO
HpFVEPvyw0nCiriZLxzTMc07vKT8YK8MR8/CI9jXV9UcH/6HRZFqlhnFO2T1OnT49HtKlMmFN5Y
F1Zqb/EUwWfarjfOY1Cf4VTrzgvRNVDIcOEd2
X-Gm-Gg: ASbGnctqlHh48IJMeGt/DDWXR8Sx/4pUmKimXTCJfqN3NNlaeoq58QT8eWncD1l43tf
w0lqJxuC6oksBoFM9oxsQfcvusnBdV022Z//4iCjwUblLe7JAwDI5WF1xDmsXgzNQ/MjtXU3xRD
GbOYAf6CRv5KTdr24Slz1/KyK4fuzdBn7LmJJgO8JkINKUDnRAmd2DTBPdSXM0ZRE=
X-Google-Smtp-Source: AGHT+IGwVGbNKMLoBUnjTKNeXs/CEhPtxalm0Jpg5PKwLDy4nVB9OJ90W7X2RENf0lgj1Zmh9aiumMfGI5D5IrWprXQ=
X-Received: by 2002:a05:622a:5c92:b0:48e:1c35:2694 with SMTP id
d75a77b69052e-494ae39944dmr35487461cf.24.1747382551953; Fri, 16 May 2025
01:02:31 -0700 (PDT)
MIME-Version: 1.0
From: Florent Carli <fcarli@gmail.com>
Date: Fri, 16 May 2025 10:02:21 +0200
X-Gm-Features: AX0GCFvRN0WhBrBTdMjrELQ8xCqcnNOEUeKKDqxbYWgaLwRs0cT_cawv2PmJDDs
Message-ID: <CAJuRqcAk8xtaXW9kRod6eq3TFteKW0_Kx8tBVA0h40hRV1S+Xg@mail.gmail.com>
Subject: Plans for Realtime Kernel and Realtime Configuration Support in Proxmox?
To: pve-devel@lists.proxmox.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-SPAM-LEVEL: Spam detection results: 0
BAYES_40 -0.001 Bayes spam probability is 20 to 40%
DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid
DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain
DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain
DMARC_PASS -0.1 DMARC pass policy
FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider
RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
X-Mailman-Approved-At: Tue, 20 May 2025 12:37:55 +0200
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=E2=80=99m currently exploring Proxmox for some use cases that require
low-latency and deterministic behavior - particularly in the context
of real-time workloads. I=E2=80=99m wondering if there are any current plan=
s
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 tun=
ing
- 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
--===============7674924432690684444==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
--===============7674924432690684444==--