Dpdk backend: optional and range match kinds translate to wildcard match for dpdk #3472
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.
Dpdk target implements both optional and range match_kind as ternary (wildcard) match
Optional match kind is essentially a ternary match where the mask is restricted to be either “every bit matches exactly”, or “every bit is wildcard”.
For the range match_kind, p4-dpdk supports it via wildcard match as long as the range can be expressed by a mask. For ex: 0..7 can be expressed using mask /0x7
P4C only needs to emit wildcard for both of these match_kinds