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

[Chassis] Update lossy profile to restrict buffer usage in congestion state (#20132) #457

Merged
merged 1 commit into from
Sep 11, 2024

Conversation

BYGX-wcr
Copy link

This is the cherry-pick PR to pick up PR: sonic-net/sonic-buildimage#20132


Why I did it
This change is to restrict lossy queue buffer usage in case of congestion state.

Work item tracking
Microsoft ADO (29315559):

How I did it
Updated alpha from 0 to -4 (400g) & -5 (100g) port speed. This configuration is applied on system port and will be using HWSKU port speed settings.

How to verify it
It is verified using sonic-mgmt tests and running ok.

Why I did it

Work item tracking
  • Microsoft ADO (number only):

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211

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)

… state (#20132)

Why I did it
This change is to restrict lossy queue buffer usage in case of congestion state.

Work item tracking
Microsoft ADO (29315559):

How I did it
Updated alpha from 0 to -4 (400g) & -5 (100g) port speed. This configuration is applied on system port and will be using HWSKU port speed settings.

How to verify it
It is verified using sonic-mgmt tests and running ok.
@BYGX-wcr BYGX-wcr merged commit be906ff into Azure:202205 Sep 11, 2024
3 checks passed
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.

2 participants