virtio — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
[PATCH v10 00/10] Introduce device group and device management
>
From: Michael S. Tsirkin <[email protected]>
> Sent: Thursday, February 9, 2023 7:13 AM
[..]
> My intent is to try and support both SR-IOV and SIOV usecases with the same
> structure and maybe even the same VQ.
>
Probably it is implicit, but is better for us to mention few examples use cases here something like,
Admin queue is an infrastructure to support use cases like:
a. SIOV devices life cycles management (create, destroy, query, configure)
b. SR-IOV VF device/resource management (SR-PCIM)
c. May be transport
> For example, it might make sense to split creating/destroying SIOV devices
> from the transport passing data from the guest - the driver would then not
> negotiate VIRTIO_F_SR_IOV (which then means auto-provisioning).
Above intermixing of SIOV and SR_IOV is very confusing.
Can you please drop it and have simpler examples like above?
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]