You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device Plugin currently is capable of pooling VFs which has been generated by SR-IOV PF NICs 0 . This setup leaves no room to just pool single PF (e.g virtio ) devices. A possible device plugin enhancement could allow the free pooling of PF devices without the need to generate and pool VFs. This enhancement could help in environments where SR-IOV NICs are not present.
Similar feature is supported by sriov-device-plugin 1 where the user is able to pool devices by just specifying the PCI adress and the driver that those devices are bound to.
Below you can see an example of pooling virtio devices by using sriov-device-plugin:
We are currently not allowing assigning PF to Client (or Endpoint in sdk-ovs I suppose). Also we expect all used devices to be SR-IOV capable, so they should have sriov_ virtual devices in /pci/bus/device/${pci_address} directory.
So I am afraid that testing SR-IOV with allowing assigning PFs and using SR-IOV incapable devices can lead us to strange bugs and undefined behavior.
Device Plugin currently is capable of pooling VFs which has been generated by SR-IOV PF NICs 0 . This setup leaves no room to just pool single PF (e.g virtio ) devices. A possible device plugin enhancement could allow the free pooling of PF devices without the need to generate and pool VFs. This enhancement could help in environments where SR-IOV NICs are not present.
Similar feature is supported by sriov-device-plugin 1 where the user is able to pool devices by just specifying the PCI adress and the driver that those devices are bound to.
Below you can see an example of pooling virtio devices by using sriov-device-plugin:
config.json: | { "resourceList": [{ "resourceName": "example_virtio_net_device", "selectors":{ "vendors": ["1af4"], "devices": ["1000"], "drivers": ["virtio-pci"], "pciAddresses": ["0000:00:0a.0", "0000:00:0b.0","0000:00:0c.0","0000:00:0d.0"] } } ] }
The text was updated successfully, but these errors were encountered: