From: Dominik Csapak <d.csapak@proxmox.com>
To: Eneko Lacunza <elacunza@binovo.es>, pve-user@lists.proxmox.com
Subject: Re: [PVE-User] vGPU scheduling
Date: Fri, 31 May 2024 10:08:57 +0200 [thread overview]
Message-ID: <1b9ebef1-5077-4ffa-8ab8-4c91639c4c7b@proxmox.com> (raw)
In-Reply-To: <cbb9c11d-5b8e-4f1a-98dd-b3e1cf4be45c@binovo.es>
On 5/31/24 09:59, Eneko Lacunza wrote:
>
> Hi Dominik,
>
> Do you have any expected timeline/version for this to be merged?
the cluster wide device mapping was merged last year already and is included in pve 8.0 and
onwards. or do you mean something different?
>
> Thanks
>
> El 25/5/23 a las 9:43, Dominik Csapak escribió:
>> On 5/25/23 09:32, DERUMIER, Alexandre wrote:
>>> Hi Dominik,
>>>
>>> any news about your patches "add cluster-wide hardware device mapping"
>>
>> i'm currently on a new version of this
>> first part was my recent series for the section config/api array support
>>
>> i think i can send the new version for the backend this week
>>
>>> ?
>>>
>>> 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 ;)
>>
>>>
>>> I think it could help for this usecase.
>>>
>>
>> yes i think so too, but it was not directly connected to the request so
>> i did not mention it
>>
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>
> Eneko Lacunza
> Zuzendari teknikoa | Director técnico
> Binovo IT Human Project
>
> Tel. +34 943 569 206 | https://www.binovo.es
> Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun
>
> https://www.youtube.com/user/CANALBINOVO
> https://www.linkedin.com/company/37269706/
>
>
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-05-31 8:08 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
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 [this message]
[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=1b9ebef1-5077-4ffa-8ab8-4c91639c4c7b@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=elacunza@binovo.es \
--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