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

Update CPU transmitted packets to queue 7 for chassis #16254

Merged
merged 2 commits into from
Aug 30, 2023

Conversation

vmittal-msft
Copy link
Contributor

@vmittal-msft vmittal-msft commented Aug 23, 2023

Why I did it

Update CPU transmitted packets to q=7 so it doesn't get impacted by other lossy traffic

Work item tracking
  • Microsoft ADO (24164290):

How I did it

Updated config file for affected HWSKUs as well as saibcm

How to verify it

It is verified on sonic chassis to be working fine.

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

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211
  • 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

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

@gechiang
Copy link
Collaborator

@vmittal-msft Can you create an ADO and add the branch info to it and update the MSFT ADO number to this PR please.
Thanks!

@vmittal-msft
Copy link
Contributor Author

@vmittal-msft Can you create an ADO and add the branch info to it and update the MSFT ADO number to this PR please. Thanks!

Done

@@ -860,3 +860,4 @@ dma_desc_aggregator_timeout_usec.BCM8869X=1000
dma_desc_aggregator_enable_specific_MDB_LPM.BCM8869X=1
dma_desc_aggregator_enable_specific_MDB_FEC.BCM8869X=1
sai_pfc_dlr_init_capability=0
sai_default_cpu_tx_tc=7
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why we need this property ? this should be controlled from SAI sonic-net/sonic-swss@04f84fc

Copy link
Collaborator

@gechiang gechiang Aug 29, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vmittal-msft , can you clarify what is the current behavior without this "default" BCM configuration specification?
Would it be up to the BRCM HWSKUs' decision on setting its own default if this is not specified?
@abdosi , Do we currently set this as part of the port attribute during port bring up? If we are not doing it currently, then having a "specified" default setting would be better than don't have it right? Otherwise, we have no way of knowing which BRCM based HWSKU default setting...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This property is needed as part of the BRCM fix for CPU to send LACP/BGP/LLDP packets on queue-7. In the absence of this property and sai fix, cpu will send packets to queue-0. for XGS platforms, we don't need this as cpu tx packets goes to queue-7.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i need to check with BRCM if this capability is supported in sai release and can be used instead.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vmittal-msft - we should request DNX SAI to support this SAI attribute.

Copy link
Contributor

@abdosi abdosi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As above comment

Copy link
Contributor

@abdosi abdosi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's follow up with BRCM via CSP

@gechiang gechiang requested a review from rlhui August 29, 2023 23:31
@rlhui rlhui merged commit 9a15221 into sonic-net:master Aug 30, 2023
20 checks passed
@gechiang
Copy link
Collaborator

@yxieca , @StormLiangMS ,
Please help cherry-pick this for corresponding branch requested under Microsoft ADO (24164290)
Thanks!!!

@mssonicbld
Copy link
Collaborator

@vmittal-msft PR conflicts with 202211 branch

@mssonicbld
Copy link
Collaborator

@vmittal-msft PR conflicts with 202205 branch

@gechiang
Copy link
Collaborator

@vmittal-msft , Please raise PR for the corresponding branch that exhibit cherry-pick conflict for both 202205 and 202211

@mssonicbld
Copy link
Collaborator

@vmittal-msft PR conflicts with 202305 branch

sonic-otn pushed a commit to sonic-otn/sonic-buildimage that referenced this pull request Sep 20, 2023
* Update CPU transmitted packets to TC = 7 for SONIC chassis

* Added new SOC property to permitted list
@StormLiangMS
Copy link
Contributor

@vmittal-msft @gechiang conflict with 202305, need separate PR.

@StormLiangMS
Copy link
Contributor

@vmittal-msft @gechiang remind for 202305 cherry pick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

7 participants