disable pfcwd for lossy platforms in deploy-mg#18350
Merged
StormLiangMS merged 5 commits intosonic-net:masterfrom May 15, 2025
Merged
disable pfcwd for lossy platforms in deploy-mg#18350StormLiangMS merged 5 commits intosonic-net:masterfrom
StormLiangMS merged 5 commits intosonic-net:masterfrom
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
sdszhang
changed the title
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
approved these changes
May 13, 2025
Co-authored-by: Dev Ojha <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
developfast
approved these changes
May 14, 2025
StormLiangMS
approved these changes
May 14, 2025
Collaborator
StormLiangMS
left a comment
StormLiangMS
left a comment
There was a problem hiding this comment.
hi @sdszhang just small question, should we use HWSKU + topo to define lossy HW? I would think same HWSKU could use for lossless scenario also, so this assumption maybe not true in that case?
Contributor
Author
these hwsku don't have lossless buffer defined in the /usr/share/sonic/device/<platform>/<hwsku> directory. so they cannot be used for lossless scenario. Currently, we don't have the scenario of using both lossless and lossy topo on same HWSKU, so should be fine. We can leave it for the future when the requirement comes in. |
Contributor
Author
|
manual cherry-pick PR to msft-202412: Azure/sonic-mgmt.msft#271 |
11 tasks
r12f
added
Approved for msft-202412 Branch
Included in msft-202412 Branch
and removed
Cherry Pick Conflict_msft-202412
labels
Collaborator
|
Cherry-pick PR to msft-202412: |
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
What is the motivation for this PR? Update the default pfcwd status in golden_config for lossy platform How did you do it? Update the default pfcwd status in golden_config for lossy platform How did you verify/test it? Verified on physical platform. Signed-off-by: opcoder0 <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
What is the motivation for this PR? Update the default pfcwd status in golden_config for lossy platform How did you do it? Update the default pfcwd status in golden_config for lossy platform How did you verify/test it? Verified on physical platform. Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
What is the motivation for this PR? Update the default pfcwd status in golden_config for lossy platform How did you do it? Update the default pfcwd status in golden_config for lossy platform How did you verify/test it? Verified on physical platform. Signed-off-by: Guy Shemesh <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
What is the motivation for this PR? Update the default pfcwd status in golden_config for lossy platform How did you do it? Update the default pfcwd status in golden_config for lossy platform How did you verify/test it? Verified on physical platform. Signed-off-by: Guy Shemesh <[email protected]>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Description of PR
Summary:
Update default_pfcwd_status to disable for some platform which only have lossy traffic.
Note: This PR needs the image fix sonic-net/sonic-utilities#3880 for it to work.
Type of change
Back port request
Approach
What is the motivation for this PR?
Update the default pfcwd status in golden_config for lossy platform
How did you do it?
Update the default pfcwd status in golden_config for lossy platform
How did you verify/test it?
Verified on physical platform.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation