From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH common/qemu-server/manager] improve vGPU (mdev) usage for NVIDIA
Date: Tue, 9 Aug 2022 10:39:06 +0200 [thread overview]
Message-ID: <287d3d9d-7a5e-f228-3685-dc0af245790b@proxmox.com> (raw)
In-Reply-To: <c7f6c5bd-ce31-ef1b-6253-e01ada414a6f@groupe-cyllene.com>
On 8/9/22 09:59, DERUMIER, Alexandre wrote:
> Le 26/07/22 à 08:55, Dominik Csapak a écrit :
>> so maybe someone can look at that and give some feedback?
>> my idea there would be to allow multiple device mappings per node
>> (instead of one only) and the qemu code would select one automatically
> Hi Dominik,
>
> do you want to create some kind of pool of pci devices in your ""add cluster-wide hardware device mapping" patches series ?
>
> Maybe in hardwaremap, allow to define multiple pci address on same node ?
>
> Then, for mdev, look if a mdev already exist in 1 of the device.
> If not, try to create the mdev if 1 device, if it's failing (max number of mdev reached), try to create mdev on the other device,...
>
> if not mdev, choose a pci device in the pool not yet detached from host.
>
yes i plan to do this in my next iteration of the mapping series
(basically what you describe)
my (rough) idea:
have a list of pci paths in mapping (e.g. 01:00.0;01:00.4;...)
(should be enough, i don't think grouping unrelated devices (different vendor/product) makes much
sense?)
* non mdev:
qemu-server checks the pci reservations (which we already have)
and takes the first not yet reserved path
* mdev
qemu-server iterates over the devices until it finds one
with the given mdev type available
if none is found, error out
(relevant bug for this: https://bugzilla.proxmox.com/show_bug.cgi?id=3574)
next prev parent reply other threads:[~2022-08-09 8:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 6:55 Dominik Csapak
2022-07-26 6:55 ` [pve-devel] [PATCH common 1/1] SysFSTools: get name from mediated device types Dominik Csapak
2022-08-12 7:25 ` Wolfgang Bumiller
2022-07-26 6:55 ` [pve-devel] [PATCH qemu-server 1/1] automatically add 'uuid' parameter when passing through NVIDIA vGPU Dominik Csapak
2022-08-12 7:32 ` Wolfgang Bumiller
2022-07-26 6:55 ` [pve-devel] [PATCH manager 1/1] ui: improve form/MDevSelector Dominik Csapak
2022-08-02 16:21 ` [pve-devel] [PATCH common/qemu-server/manager] improve vGPU (mdev) usage for NVIDIA DERUMIER, Alexandre
2022-08-09 7:59 ` DERUMIER, Alexandre
2022-08-09 8:39 ` Dominik Csapak [this message]
2022-08-16 23:15 ` DERUMIER, Alexandre
2022-08-22 10:16 ` Dominik Csapak
2022-08-22 13:39 ` DERUMIER, Alexandre
2022-08-22 14:07 ` Dominik Csapak
2022-08-23 7:50 ` 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=287d3d9d-7a5e-f228-3685-dc0af245790b@proxmox.com \
--to=d.csapak@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