From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>,
Alexandre Derumier <aderumier@odiso.com>
Subject: Re: [PVE-User] vGPU scheduling
Date: Thu, 25 May 2023 11:03:58 +0200 [thread overview]
Message-ID: <95557018-6e02-d720-752e-5ff33a8e386b@proxmox.com> (raw)
In-Reply-To: <374604f3-c28b-5ed4-0d58-c1bcc6473c05@proxmox.com>
Am 25/05/2023 um 09:43 schrieb Dominik Csapak:
>>
>> Do you think it'll be merged for proxmox 8 ?
>
> i don't know, but this also depends on the capacity of my colleagues to review 😉
making it easy to digest and adding (good) tests will surely help to
accelerate this ;-P
But, you're naturally right, and tbh., while I'll try hard to get the access-control
and some other fundaments in, especially those where we can profit from the higher
freedom/flexibility of a major release, I cannot definitely say that the actual HW
mapping will make it for initial 8.0.
For initial major release I prefer having a bit less features but focus more on that
the existing features keep working and that there's a stable and well tested upgrade path.
next prev parent reply other threads:[~2023-05-25 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.190.1684933430.348.pve-user@lists.proxmox.com>
2023-05-24 13:47 ` Dominik Csapak
2023-05-25 7:32 ` DERUMIER, Alexandre
2023-05-25 7:43 ` Dominik Csapak
2023-05-25 9:03 ` Thomas Lamprecht [this message]
2024-05-31 7:59 ` Eneko Lacunza via pve-user
[not found] ` <cbb9c11d-5b8e-4f1a-98dd-b3e1cf4be45c@binovo.es>
2024-05-31 8:08 ` Dominik Csapak
[not found] ` <mailman.193.1684936457.348.pve-user@lists.proxmox.com>
[not found] ` <mailman.222.1684948008.348.pve-user@lists.proxmox.com>
[not found] ` <0e48cb4a-7fa0-2bd7-9d4e-f18ab8e03d20@proxmox.com>
[not found] ` <mailman.252.1685000179.348.pve-user@lists.proxmox.com>
2023-05-25 7:53 ` Dominik Csapak
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=95557018-6e02-d720-752e-5ff33a8e386b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=aderumier@odiso.com \
--cc=d.csapak@proxmox.com \
--cc=pve-user@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