Dpdk Backend: Fix non-consecutive table keys for add_on_miss table #3763
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.
For Add_on_miss tables, DPDK target expects the table keys to be in consecutive location in the underlying structure.
When tables keys are combination of header and metadata fields, only header field was getting copied to metadata where we should also copy the metadata fields to make them consecutive in metadata structure. The metadata copy should always be done for learner table if the keys are not contiguous.