PSA/eBPF: retrieve interface numbers from OS in PTF tests #3659
Conversation
This file contains 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
Co-authored-by: Jan Palimąka <25018671+tatry@users.noreply.github.com>
mihaibudiu
approved these changes
Nov 3, 2022
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.
Previously, we hardcoded interface numbers in PTF tests and P4 programs. However, PTF tests will fail if OS changes the numbering for some reason. I met this issue when running PTF tests for PSA/eBPF in Docker for Mac VM.
This PR modifies the PTF framework used for eBPF so that:
DP_PORTSdictonaryPORTxmacros to inject retrieved interface numbers to P4 programsDP_PORTSdictonary to find a real interface number