Skip to content
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

[PR tracker] Add new ACL key BTH_OPCODE and AETH_SYNDROME #1245

Closed
wants to merge 1 commit into from

Conversation

Junchao-Mellanox
Copy link
Contributor

This is just a dummy PR to record feature "Add new ACL key BTH_OPCODE and AETH_SYNDROME". DON'T merge this.

Feature Description

BTH OPCODE and AETH SYNDROME are fields in RoCEv2 packet. This feature enable user matching these two fields via ACL rule.

Vendor should support following SAI attributes:

  • SAI_ACL_TABLE_ATTR_FIELD_BTH_OPCODE
  • SAI_ACL_TABLE_ATTR_FIELD_AETH_SYNDROME
  • SAI_ACL_ENTRY_ATTR_FIELD_BTH_OPCODE
  • SAI_ACL_ENTRY_ATTR_FIELD_AETH_SYNDROME

Related PRs

PR title state context
[sonic-acl.yang] Add new ACL key BTH_OPCODE and AETH_SYNDROME GitHub issue/pull request detail GitHub pull request check contexts
[acl] Add new ACL key BTH_OPCODE and AETH_SYNDROME GitHub issue/pull request detail GitHub pull request check contexts

@liat-grozovik liat-grozovik changed the title Add new ACL key BTH_OPCODE and AETH_SYNDROME [PR tracker] Add new ACL key BTH_OPCODE and AETH_SYNDROME Feb 6, 2023
@liat-grozovik
Copy link
Collaborator

@zhangyanzhao should we close the tracking PR now that the code changes are merged?

@liat-grozovik
Copy link
Collaborator

@zhangyanzhao should we close the tracking PR now that the code changes are merged?

@zhangyanzhao kindly reminder, what should we do with a tracking PR when all PRs are merged? should it be closed? labeled somehow?

@zhangyanzhao
Copy link
Collaborator

Tracking PR and code PRs are merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants