[Qos]Updating J2C+ qos yaml for 400G lossy profile#14802
Merged
arlakshm merged 1 commit intosonic-net:masterfrom Nov 7, 2024
Merged
[Qos]Updating J2C+ qos yaml for 400G lossy profile#14802arlakshm merged 1 commit intosonic-net:masterfrom
arlakshm merged 1 commit intosonic-net:masterfrom
Conversation
Contributor
Author
|
@vmittal-msft ,please review. |
vmittal-msft
approved these changes
Oct 28, 2024
Contributor
arlakshm
approved these changes
Nov 7, 2024
Contributor
Author
|
PR # #15448 raised for 202405 |
sreejithsreekumaran
pushed a commit
to sreejithsreekumaran/sonic-mgmt
that referenced
this pull request
Nov 15, 2024
Fixing intermittent failure in lossy queue by adjusting the pkts_num_trig_egr_drp for 'broadcom-dnx' t2 chassis. Updation on the original PR # sonic-net#14585 Summary: Fixes # (issue) Type of change Bug fix Testbed and Framework(new/improvement) Test case(new/improvement) Back port request 202012 202205 202305 202311 202405 Approach What is the motivation for this PR? How did you do it? Since the pkts_num_leakout is more for 100G.Adjusting the count of pkt sent to trigger egress drop. How did you verify/test it? Executed the qos test and verify.
Contributor
Author
|
@arlakshm , please add tag for 202205 |
Contributor
|
@wangxin can we merge these changes to 202205 ? |
yutongzhang-microsoft
pushed a commit
to yutongzhang-microsoft/sonic-mgmt
that referenced
this pull request
Nov 21, 2024
Fixing intermittent failure in lossy queue by adjusting the pkts_num_trig_egr_drp for 'broadcom-dnx' t2 chassis. Updation on the original PR # sonic-net#14585 Summary: Fixes # (issue) Type of change Bug fix Testbed and Framework(new/improvement) Test case(new/improvement) Back port request 202012 202205 202305 202311 202405 Approach What is the motivation for this PR? How did you do it? Since the pkts_num_leakout is more for 100G.Adjusting the count of pkt sent to trigger egress drop. How did you verify/test it? Executed the qos test and verify.
Contributor
Author
|
@wangxin , can you please merge this change to 202205. |
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
3 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
Fixing intermittent failure in lossy queue by adjusting the pkts_num_trig_egr_drp for 'broadcom-dnx' t2 chassis.
Updation on the original PR # #14585
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
Since the pkts_num_leakout is more for 100G.Adjusting the count of pkt sent to trigger egress drop.
How did you verify/test it?
Executed the qos test and verify.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation