-
Notifications
You must be signed in to change notification settings - Fork 484
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
Class-Based Forwarding #1193
Class-Based Forwarding #1193
Conversation
@JaiOCP , @marian-pritsak , @ashutosh-agrawal - would you like to review/sign-off this? Thanks. |
@j-bos - thanks. possible to also upload the ppt to https://github.com/opencomputeproject/SAI/tree/master/doc/ECMP? |
@j-bos - please check the DCO error if this can be resolved. |
Since we do not have an explicit capability check, can you spell out the mechanism to know whether a SAI implementation supports this capability. Say, if SAI_SWITCH_ATTR_MAX_NUMBER_OF_FORWARDING_CLASSES is 0? |
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.
We need to enhance the SAI behavioral model to accommodate this change.
Concept of Internal Class as an index in ECMP Group need to come from ACL table.
Today Next Hop Group block has a match only on next hop group hash value. This need to be explicitly enhanced to include class id.
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.
Raising this question to capture in review.
Given the concept of class id based ECMP group indexing is a specific implementation to silicon and is not RFC based: Should it be not part of SAI extensions?
The most direct would be an enum-capability for next-hop group type (class-based). Though, I think a check if SAI_SWITCH_ATTR_MAX_NUMBER_OF_FORWARDING_CLASSES is supported and non-zero would be reasonable as well. |
@lguohan - would you like to review? Thanks. |
@marian-pritsak , please also help review, thanks. |
Resolved |
please resolve conflicts |
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
@j-bos Are you working on update using new object ? |
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
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.
Please update the pipeline with CBF and ECMP stage indicated as optional.
/azp run |
Pull request contains merge conflicts. |
please resolve conflicts |
Signed-off-by: Jason Bos <jbos@cisco.com>
…YPE_MAX to change Signed-off-by: Jason Bos <jbos@cisco.com>
Adjust to provide a representation of optional steps in the behavioral model diagram. Dashed border by itself was hard to see, so used a hash-fill as well. Signed-off-by: Jason Bos <jbos@cisco.com>
Signed-off-by: Jason Bos <jbos@cisco.com>
Done |
This check will make sure that enum values are constant from this point on all future commits. [meta] Add enum ancestry check on SAI includes (opencomputeproject#1297) Will make sure that from BEGIN_COMMIT we will be always backward compatible for SAI enums Class-Based Forwarding (opencomputeproject#1193) This PR defines class-based forwarding. It contains two aspects: Assignment of a Forwarding Class to a packet, via QOS map or ACL New next-hop group type: SAI_NEXT_HOP_GROUP_TYPE_CLASS_BASED Where member selection is based on the forwarding-class of the packet. Signed-off-by: Jason Bos <jbos@cisco.com> [tests] Add missing lib -lzmq to saithrift (opencomputeproject#1298) [meta] Make sure SAI version components are unsigned integers (opencomputeproject#1300) [meta] Add lower case notification names (opencomputeproject#1301)
This PR defines class-based forwarding. It contains two aspects: Assignment of a Forwarding Class to a packet, via QOS map or ACL New next-hop group type: SAI_NEXT_HOP_GROUP_TYPE_CLASS_BASED Where member selection is based on the forwarding-class of the packet. Signed-off-by: Jason Bos <jbos@cisco.com>
This PR defines class-based forwarding. It contains two aspects: Assignment of a Forwarding Class to a packet, via QOS map or ACL New next-hop group type: SAI_NEXT_HOP_GROUP_TYPE_CLASS_BASED Where member selection is based on the forwarding-class of the packet. Signed-off-by: Jason Bos <jbos@cisco.com>
This PR defines class-based forwarding. It contains two aspects: Assignment of a Forwarding Class to a packet, via QOS map or ACL New next-hop group type: SAI_NEXT_HOP_GROUP_TYPE_CLASS_BASED Where member selection is based on the forwarding-class of the packet. Signed-off-by: Jason Bos <jbos@cisco.com>
This PR defines class-based forwarding. It contains two aspects:
Assignment of a Forwarding Class to a packet, via QOS map or ACL
New next-hop group type: SAI_NEXT_HOP_GROUP_TYPE_CLASS_BASED
Where member selection is based on the forwarding-class of the packet.
Signed-off-by: j-bos jbos@cisco.com