Skip to content

Update the buffer pool sizes based on the latest algorithm#28610

Open
stephenxs wants to merge 1 commit into
sonic-net:masterfrom
stephenxs:upstream-update-spc6-buffer
Open

Update the buffer pool sizes based on the latest algorithm#28610
stephenxs wants to merge 1 commit into
sonic-net:masterfrom
stephenxs:upstream-update-spc6-buffer

Conversation

@stephenxs

Copy link
Copy Markdown
Collaborator

Why I did it

The SN6600 buffer pool sizes needed to be aligned with the latest buffer-sizing calculations.

Work item tracking
  • Microsoft ADO (number only):

How I did it

Updated the ingress lossless, ingress lossy, egress lossless, and egress lossy pool sizes for the affected SN6600 physical and simx SKUs. Applied the calculated values consistently to both T0 and T1
buffer templates.

How to verify it

  • Recalculate the affected SKUs using the latest buffer-sizing Excel workbook.
  • Confirm that the generated pool sizes match the values in the updated Jinja2 templates.
  • Verify that corresponding physical and simx SKUs use consistent values.
  • Generate the buffer configuration for the affected T0 and T1 SKUs and confirm that it renders successfully.

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

  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511
  • 202512
  • 202605
  • 202608

Tracking issue/work item for backport/cherry-pick request (GitHub issue or Microsoft ADO):
Failure type:

Tested branch

  • master
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505
  • 202511
  • 202512
  • 202605
  • 202608
  • N/A

Test result

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: Stephen Sun <stephens@nvidia.com>
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run Azure.sonic-buildimage

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

@jianyuewu
jianyuewu self-requested a review July 24, 2026 01:01
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.

3 participants