Adding support for Intel Fortville + DPDK use-case#155
Merged
Conversation
35d1a30 to
e3d6618
Compare
Collaborator
Author
|
Actually... This greatly streamlines execution paths, and allows to finally get rid of our own IPVLAN interface handling module. All special features originally working only for IPVLAN are now 100% work for everything - even for VFIO bound PCI devices! |
…nterfaces. This enables us to: - handle ALL activities, in one place, unconditionally - cleaner code - finally getting rid of all IPVLAN specific code - being able to apply post processing even for the dummy interfaces
ffd7d71 to
1429374
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR solves bullet point 2 described in #148.
It also makes sure to skip kernel tunings for interfaces which are actually not managed by the kernel.