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

Dpdk backend: optional and range match kinds translate to wildcard match for dpdk #3472

Merged
merged 1 commit into from
Aug 3, 2022

Conversation

usha1830
Copy link
Contributor

@usha1830 usha1830 commented Aug 3, 2022

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

@mihaibudiu mihaibudiu merged commit d3a55bb into p4lang:main Aug 3, 2022
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.

2 participants