Skip to content
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

Enhancing dummy interface capabilities with VLAN and PCI ID information #214

Merged
merged 3 commits into from
Apr 28, 2020

Conversation

Levovar
Copy link
Collaborator

@Levovar Levovar commented Apr 27, 2020

solves #175
When the VFIO bound VF is tagged with a VLAN, we create an extra VLAN IF on top of the dummy with the same tag.
The VF's PCI ID is added to the dummy (VLAN too) as an Alias.
This mapping should be enough for applications to map allocations to the proper device.

When the VFIO bound VF is tagged with a VLAN, we create an extra VLAN IF on top of the dummy with the same tag.
The VF's PCI ID is added to the dummy (VLAN too) as an Alias.
This mapping should be enough for applications to map allocations to the proper device.
@Levovar
Copy link
Collaborator Author

Levovar commented Apr 27, 2020

added possible way of creating dummy interface with the VF's original MAC address

also fixed a regression related to SR-IOV handling... well... being totally broken for a time now
oopsie

I have absolutely no idea when, but SR-IOV Device Management broke at some point due to not setting DeviceID into DanmEp.
This is now fixed, SR-IOV works again as intended.
In addition to that MAC address is also saved into DanmEp for VFs, and used to make dummy interfaces.
The dummy NICs will be provisioned with the MAC of the VF, even if they are bound to a user space driver.
Also expanded user documentation with the additional feature.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant