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

Updating ingress drop counters for 100G_120k profile in qos #10146

Merged
merged 1 commit into from
Oct 2, 2023

Conversation

ansrajpu-git
Copy link
Contributor

Description of PR

Aligning to the change in PR# sonic-net/sonic-buildimage#16690
Summary:
The ingress drop counter value adjusted in qos_params.j2c to align with change in total headroom pool size (PR#16690 )
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

PCFXoff test cases failure

How did you do it?

How did you verify/test it?

Executed qos test for T2 topology.

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202205: #10389

@mssonicbld
Copy link
Collaborator

Cherry-pick PR to 202305: #10576

arlakshm pushed a commit that referenced this pull request Feb 13, 2024
The J2c+ qos params for 100_120K was updated in #10146 but it wasn't updated for J2.
This has caused failures on testQosSaiPfcXoffLimit because we aren't sending sufficient packets to fill up the headroom so packets aren't being dropped.

I confirmed on a J2 system with these new values we end up filling up the headroom and drop packets.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants