[action] [PR:12765] Update nexthop rewrite for flows based on default hash offset #13871
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
…net#12765) Update nexthop rewrites for Cisco asics after updating the default hash offset values.
3 tasks
|
Original PR: #12765 |
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.
Description of PR
Update nexthop rewrites for Cisco asics after updating the default hash offset values.
Summary:
Fixes # (issue)
Type of change
T1 default hash offset values are changed by PRs:
sonic-net/sonic-swss#3138
sonic-net/sonic-buildimage#18912
Update the flow rewrites with the hash offset value changes.
Approach
What is the motivation for this PR?
Updating the flow rewrites after hash offset value changes.
How did you verify/test it?
Verified by running "ipfwd/test_nhop_group.py::test_nhop_group_member_order_capability" on various platforms.
Any platform specific information?
This PR to be merged after:
sonic-net/sonic-swss#3138
sonic-net/sonic-buildimage#18912