Update SN6810 buffer pool sizes from latest calculation#28615
Open
jianyuewu wants to merge 1 commit into
Open
Conversation
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
Apply the revised SPC6 pool allocation to physical and simulation SKUs. Signed-off-by: Jianyue Wu <jianyuew@nvidia.com>
jianyuewu
force-pushed
the
master-update-cham6-buffer
branch
from
July 24, 2026 09:37
8efe15b to
638b510
Compare
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
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
2 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.
Apply the revised Cham6 pool allocation to physical and simulation SKUs.
Why I did it
The Cham6 buffer pool sizes needed to be aligned with the latest buffer-sizing Excel calculations.
How I did it
Updated the ingress lossless, ingress lossy, egress lossless, and egress lossy pool sizes for the affected Cham6 physical and simx SKUs. Applied the calculated values consistently to both T0 and T1 buffer templates.
How to verify it
Recalculate the affected Cham6 SKUs using the latest buffer-sizing Excel workbook.
Confirm that the generated pool sizes match 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)
Tested branch
Test result
Test pass in Cham6 switch.