-
Notifications
You must be signed in to change notification settings - Fork 530
Next hop group attribute to specify if weights are achieved by repeating members or via the weighting support in the hardware.. #2166
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
base: master
Are you sure you want to change the base?
Conversation
…ogrammed by repeating the next hop members in proportion to their weight or by using the intrinsic next hop group weight support in the hardware. Signed-off-by: Kishore Gummadidala <[email protected]>
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need more understanding so as to standardize the expected behavior.
* | ||
* @type bool | ||
* @flags CREATE_AND_SET | ||
* @default false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default value of "false" will NOT be backward compatible for devices that support Native WCMP.
The name of this attribute must be SAI_NEXT_HOP_GROUP_ATTR_DISABLE_NATIVE_WCMP with default value as False.
@@ -299,6 +299,17 @@ typedef enum _sai_next_hop_group_attr_t | |||
*/ | |||
SAI_NEXT_HOP_GROUP_ATTR_LABEL, | |||
|
|||
/** | |||
* @brief Weighted multi path configuration mode. | |||
* false: Nexthop group is programmed with repeated member entries proportional to their weight |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the SAI implementation repeats next hop group member entries, should the SAI_SWITCH_ATTR_AVAILABLE_NEXT_HOP_GROUP_MEMBER_ENTRY attribute be updated to reflect the count of the repeated entries, or should it be based on the number of unique members in the ASIC_DB?
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@erohsik - could you please help address the comments? |
Add new next hop group attribute to specify if a next hop group is programmed by repeating the next hop members in proportion to their weight or by using the intrinsic next hop group weight support in the hardware.