-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Update PG flow control threshold based on port speed (not on hwsku) #21733
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
arlakshm
approved these changes
Feb 13, 2025
saksarav-nokia
approved these changes
Feb 13, 2025
ram25794
pushed a commit
to ram25794/sonic-buildimage
that referenced
this pull request
Feb 21, 2025
…onic-net#21733) Why I did it To update PG flow control threshold alpha value based on port speed. Current assumption was based on hwsku. Work item tracking Microsoft ADO (31374200): How I did it Updated pg_profile.ini for various HW SKUs based on BRCM j2/j2c+ chip
Merged
11 tasks
Cherry-pick PR to 202411: #21834 |
12 tasks
prabhataravind
pushed a commit
to prabhataravind/sonic-buildimage
that referenced
this pull request
Mar 5, 2025
…onic-net#21733) Why I did it To update PG flow control threshold alpha value based on port speed. Current assumption was based on hwsku. Work item tracking Microsoft ADO (31374200): How I did it Updated pg_profile.ini for various HW SKUs based on BRCM j2/j2c+ chip
11 tasks
Cherry-pick PR to msft-202405: Azure/sonic-buildimage-msft#983 |
yanjundeng
pushed a commit
to yanjundeng/sonic-buildimage
that referenced
this pull request
Apr 23, 2025
…onic-net#21733) Why I did it To update PG flow control threshold alpha value based on port speed. Current assumption was based on hwsku. Work item tracking Microsoft ADO (31374200): How I did it Updated pg_profile.ini for various HW SKUs based on BRCM j2/j2c+ chip
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
To update PG flow control threshold alpha value based on port speed. Current assumption was based on hwsku.
Work item tracking
How I did it
Updated pg_profile.ini for various HW SKUs based on BRCM j2/j2c+ chip
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)