[Mellanox] Adjust buffer parameters with 2km cable supported for 4600C non-generic SKUs #9215
Conversation
Also recalculated all parameters with the latest algorithm with per-speed peer response time taken into account Detailed information of each SKU: - C64: 32 100G down links and 32 100G up links with 2km cable supported on t1 - D112C8: 112 50G down links and 8 100G up links. - D48C40: 48 50G down links, 32 100G down links and 8 100G up links - D100C12S2: 4 100G down links, 2 10G down links, 100 50G down links and 8 100G uplinks 2km cable is supported for C64 on t1 only Signed-off-by: Stephen Sun <stephens@nvidia.com>
|
It can be cherry-picked to 202012 cleanly. |
Signed-off-by: Stephen Sun <stephens@nvidia.com>
|
/azpw run azure.sonic-buildimage |
|
/AzurePipelines run azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
|
/azpw run azure.sonic-buildimage |
|
/AzurePipelines run azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@stephenxs if this was taken into consideration new logic resides only on master/202111 I don't think we should set the label as it cannot be cleanly cherry picked |
As offline discussed, it isn't related to the per speed peer response time for dynamic buffer calculation. So let's request it for 202012 and 202106 (after PR #8242 being cherry-picked). |
device/mellanox/x86_64-mlnx_msn4600c-r0/Mellanox-SN4600C-D112C8/pg_profile_lookup.ini
Show resolved
Hide resolved
Add "Request for 202106" as the dependent PR has been cherry-picked. |
…C non-generic SKUs (#9215) - Why I did it Also recalculated all parameters with the latest algorithm with per-speed peer response time taken into account - How I did it Detailed information of each SKU: C64: t0: 32 100G downlinks and 32 100G uplinks t1: 56 100G downlinks and 8 100G uplinks with 2km-cable supported D112C8: 112 50G downlinks and 8 100G uplinks. D48C40: 48 50G downlinks, 32 100G downlinks, and 8 100G uplinks D100C12S2: 4 100G downlinks, 2 10G downlinks, 100 50G downlinks, and 8 100G uplinks 2km cable is supported for C64 on t1 only - How to verify it Run regression test (QoS) Signed-off-by: Stephen Sun <stephens@nvidia.com>
stephenxs
added
the
Request for 202111 Branch
…C non-generic SKUs (#9215) - Why I did it Also recalculated all parameters with the latest algorithm with per-speed peer response time taken into account - How I did it Detailed information of each SKU: C64: t0: 32 100G downlinks and 32 100G uplinks t1: 56 100G downlinks and 8 100G uplinks with 2km-cable supported D112C8: 112 50G downlinks and 8 100G uplinks. D48C40: 48 50G downlinks, 32 100G downlinks, and 8 100G uplinks D100C12S2: 4 100G downlinks, 2 10G downlinks, 100 50G downlinks, and 8 100G uplinks 2km cable is supported for C64 on t1 only - How to verify it Run regression test (QoS) Signed-off-by: Stephen Sun <stephens@nvidia.com>
…C non-generic SKUs (#9215) - Why I did it Also recalculated all parameters with the latest algorithm with per-speed peer response time taken into account - How I did it Detailed information of each SKU: C64: t0: 32 100G downlinks and 32 100G uplinks t1: 56 100G downlinks and 8 100G uplinks with 2km-cable supported D112C8: 112 50G downlinks and 8 100G uplinks. D48C40: 48 50G downlinks, 32 100G downlinks, and 8 100G uplinks D100C12S2: 4 100G downlinks, 2 10G downlinks, 100 50G downlinks, and 8 100G uplinks 2km cable is supported for C64 on t1 only - How to verify it Run regression test (QoS) Signed-off-by: Stephen Sun <stephens@nvidia.com>
Why I did it
Also recalculated all parameters with the latest algorithm with per-speed peer response time taken into account
Signed-off-by: Stephen Sun stephens@nvidia.com
How I did it
Detailed information of each SKU:
2km cable is supported for C64 on t1 only
How to verify it
Run regression test (QoS)
Which release branch to backport (provide reason below if selected)
Description for the changelog
A picture of a cute animal (not mandatory but encouraged)