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

Minigraph parser changes to select mmu profiles based on SonicQosProfile attribute #11429

Merged
merged 2 commits into from
Jul 13, 2022

Conversation

neethajohn
Copy link
Contributor

Why I did it

There is a need to select different mmu profiles based on deployment type

How I did it

There will be separate subfolders (RDMA-CENTRIC, TCP-CENTRIC, BALANCED) in each hwsku folder which contains deployment specific mmu and qos settings. SonicQosProfile attribute in the minigraph will be used to determine which settings to use. If that attribute is not present, the default settings that exist in the hwsku folder will be used

How to verify it

Signed-off-by: Neetha John <nejo@microsoft.com>
Signed-off-by: Neetha John <nejo@microsoft.com>
@neethajohn neethajohn marked this pull request as ready for review July 13, 2022 16:08
@neethajohn neethajohn requested a review from a team as a code owner July 13, 2022 16:08
@neethajohn neethajohn requested a review from yxieca July 13, 2022 16:08
@neethajohn neethajohn merged commit 23308a3 into sonic-net:master Jul 13, 2022
@neethajohn neethajohn deleted the qos_profile_parser_master branch July 13, 2022 22:25
yxieca pushed a commit that referenced this pull request Jul 17, 2022
…ile attribute (#11429)

Signed-off-by: Neetha John <nejo@microsoft.com>

Why I did it
There is a need to select different mmu profiles based on deployment type

How I did it
There will be separate subfolders (RDMA-CENTRIC, TCP-CENTRIC, BALANCED) in each hwsku folder which contains deployment specific mmu and qos settings. SonicQosProfile attribute in the minigraph will be used to determine which settings to use. If that attribute is not present, the default settings that exist in the hwsku folder will be used
skbarista pushed a commit to skbarista/sonic-buildimage that referenced this pull request Aug 17, 2022
…ile attribute (sonic-net#11429)

Signed-off-by: Neetha John <nejo@microsoft.com>

Why I did it
There is a need to select different mmu profiles based on deployment type

How I did it
There will be separate subfolders (RDMA-CENTRIC, TCP-CENTRIC, BALANCED) in each hwsku folder which contains deployment specific mmu and qos settings. SonicQosProfile attribute in the minigraph will be used to determine which settings to use. If that attribute is not present, the default settings that exist in the hwsku folder will be used
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants