-
Notifications
You must be signed in to change notification settings - Fork 648
[SWSS] Enhance the hash-setting code to account for SAI_SWITCH_ATTR_ECMP/LAG_HASH_IPV4/V6 #3971
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
Open
sriharsha-nexthop
wants to merge
1
commit into
sonic-net:master
Choose a base branch
from
sriharsha-nexthop:sriharsha.v4v6-hash-changes
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[SWSS] Enhance the hash-setting code to account for SAI_SWITCH_ATTR_ECMP/LAG_HASH_IPV4/V6 #3971
sriharsha-nexthop
wants to merge
1
commit into
sonic-net:master
from
sriharsha-nexthop:sriharsha.v4v6-hash-changes
+225
−27
Conversation
This file contains hidden or 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
Collaborator
|
/azp run |
|
|
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
|
/azpw run Azure.sonic-swss |
Collaborator
|
/AzurePipelines run Azure.sonic-swss |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
7183033 to
5afa2ca
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
|
/azpw run Azure.sonic-swss |
Collaborator
|
/AzurePipelines run Azure.sonic-swss |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Fixes : #3986
What I did
Why I did it
For setting the global hash-fields, SONIC currently uses SAI_SWITCH_ATTR_ECMP/LAG_HASH.
However, Broadcom SAI only supports SAI_SWITCH_ATTR_ECMP/LAG_HASH_IPV4/6.
Hence, enhancing the hash-field support to include Broadcom SAI.
Also, Broadcom platform doesn't accept setting the fields with SAI_NULL_OBJECT_ID.
It needs the SONIC to create hash objects (for v4 and v6) and use them to set the hash-fields.
Also, since Broadcom SAI would've set some default values, they need to be cleared before setting new field-list.
How I verified it
Since this can not be verified on VS, I ran the command on Broadcom platform and used bcm shell commands to verify that correct fields are set.
Before the change
After the change
Details if related