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

[action] [PR:3136] Use shared egress ACL table for PFCWD in BRCM DNX platform (#3136) #3250

Merged
merged 1 commit into from
Aug 3, 2024

Conversation

mssonicbld
Copy link
Collaborator

  • Use shared egress ACL table for PFCWD in BRCM DNX platform.

Today PFCWD uses separate egress ACL tables, one table for each traffic class.
This may result in ACL resource overflow when other features that also need
egress ACL table is enabled at the same time, e.g., MACSEC. ( See
sonic-net/sonic-buildimage#17839 for details).

The fix is to use shared egress ACL table for PFCWD in BRCM DNX platform.

…#3136)

* Use shared egress ACL table for PFCWD in BRCM DNX platform.

Today PFCWD uses separate egress ACL tables, one table for each traffic class.
This may result in ACL resource overflow when other features that also need
egress ACL table is enabled at the same time, e.g., MACSEC. ( See
sonic-net/sonic-buildimage#17839 for details).

The fix is to use shared egress ACL table for PFCWD in BRCM DNX platform.
@mssonicbld
Copy link
Collaborator Author

Original PR: #3136

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

Successfully merging this pull request may close these issues.

2 participants