-
Notifications
You must be signed in to change notification settings - Fork 489
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
Add a new attribute SAI_BFD_SESSION_ATTR_NEXT_HOP_ID to saibfd.h #2127
base: master
Are you sure you want to change the base?
Add a new attribute SAI_BFD_SESSION_ATTR_NEXT_HOP_ID to saibfd.h #2127
Conversation
/app run |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Skipping cap file sample.cap |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
you are causing enum shift:
all attributes needs to be added at the end, also you need to force push to single commit all changes with enum shift |
Signed-off-by: Baorong Liu <[email protected]> remove extra space Signed-off-by: Baorong Liu <[email protected]> move new added attr to the end of enum Signed-off-by: Baorong Liu <[email protected]>
3838d9d
to
4fb9d00
Compare
updated and squashed old commits to a single commit. thanks |
/azp run |
Commenter does not have sufficient privileges for PR 2127 in repo opencomputeproject/SAI |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@baorliu - would you like to discuss this PR in this week's community meeting? |
in the middle of validating it in a system now. we can discuss it after I verify the use case with the new attributes. |
<re-created the PR, because the original one #2117 was using master branch in forked repo cause the commits were lost when do fork sync.
Please see comments in #2117 for review history>
Adding a new attribute SAI_BFD_SESSION_ATTR_NEXT_HOP_ID to saibfd.h to support forwarding single hop bfd packet to specific nexthop.
The proposed usage is:
1, this attribute can be provided both in create_bfd_session and set_bfd_session_attribute.
2, if SAI_BFD_SESSION_ATTR_USE_NEXT_HOP (optional, default is false) is set to true, BFD session will get next hop from SAI_BFD_SESSION_ATTR_NEXT_HOP_ID value and forward the bfd packet to the next hop. If SAI_BFD_SESSION_ATTR_USE_NEXT_HOP is false, attribute SAI_BFD_SESSION_ATTR_NEXT_HOP_ID will be ignored.
3, when using both SAI_BFD_SESSION_ATTR_HW_LOOKUP_VALID and SAI_BFD_SESSION_ATTR_USE_NEXT_HOP, the implementation is vender dependent.