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

td2/td3 change cpu cos num to 10 #9301

Merged
merged 1 commit into from
Nov 18, 2021
Merged

td2/td3 change cpu cos num to 10 #9301

merged 1 commit into from
Nov 18, 2021

Conversation

prsunny
Copy link
Contributor

@prsunny prsunny commented Nov 18, 2021

Why I did it

bcm_num_cos=10 forces SDK default to map internal priority 0-7 to COS 0. It is now consistent with other SKUs.

How I did it

Modified config.bcm

How to verify it

Verified the Cosq for trapped packets

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106

Description for the changelog

A picture of a cute animal (not mandatory but encouraged)

@lguohan lguohan merged commit d6c3a93 into sonic-net:master Nov 18, 2021
Copy link
Collaborator

@gechiang gechiang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we consider S6000 HW SKUs as well? They are also TD2 based I think...

@prsunny
Copy link
Contributor Author

prsunny commented Nov 18, 2021

Should we consider S6000 HW SKUs as well? They are also TD2 based I think...

@gechiang, its already set as 10 for S6000.

@prsunny prsunny deleted the cos_map branch November 18, 2021 05:14
@gechiang
Copy link
Collaborator

Should we consider S6000 HW SKUs as well? They are also TD2 based I think...

@gechiang, its already set as 10 for S6000.

That's great! Thanks!

lguohan pushed a commit that referenced this pull request Nov 18, 2021
@qiluo-msft
Copy link
Collaborator

This commit could not be cleanly cherry-picked to 202012. Please submit another PR.

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.

4 participants