-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use VFs from the same PF for different modes (netlink, vfio, ...) #80
Comments
@booxter Actually, you can achieve this with current implementation without any changes. Let me give you an example. Say you have a PF with 4 VFs: 00:01.0, 00:01.1 with vfio-pci and 00:01.2, 00:01.3 with netdev driver. You can have two resource pool endpoints as follows:
The "rootDevice" contains the pci address of the VFs regardless of what PFs they belong to. In this case you cannot mix this with PF's pci address and "sriovMode": should be false. Only penalty is you're gonna have to provide each VF's pci address by hand in the config file. Where in, with PF's pci address and "sriovMode": true will let you discover these VFs pci address dynamically. |
I think this can be accomplished with above configuration. And with new selector based config, this can also be achieved by using driver selector to distinguish VFs of different mode. |
When there is a single PF on a host, or one would like to reuse the same PF for multiple types of workloads, right now it's impossible because device plugin is configured on per-PF basis. We should have a way to split out particular VFs to use for one type and the rest for another type; or to not use part of available VFs at all. (The latter is useful when some VFs are utilized for hypervisor network connectivity.)
This can be achieved by either allowing to specify VF and not just PF IDs in
config.json
.The text was updated successfully, but these errors were encountered: