Skip to content

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

erohsik
Copy link
Contributor

@erohsik erohsik commented Apr 23, 2025

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.

…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]>
@tjchadaga
Copy link
Collaborator

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@rck-innovium rck-innovium left a 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
Copy link
Contributor

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
Copy link
Contributor

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?

@tjchadaga tjchadaga added the reviewed PR is discussed in SAI Meeting label Apr 28, 2025
@kcudnik
Copy link
Collaborator

kcudnik commented May 23, 2025

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@tjchadaga
Copy link
Collaborator

@erohsik - could you please help address the comments?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reviewed PR is discussed in SAI Meeting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants