Add meter_type packets when creating blocking scheduler#21436
Add meter_type packets when creating blocking scheduler#21436StormLiangMS merged 1 commit intosonic-net:masterfrom
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
d840c81 to
96bbcc8
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
r12f
left a comment
There was a problem hiding this comment.
straight forward fix. lgtm.
|
I verify this PR on x86_64-nvidia_sn5640-r0 platform, we do not the support the new parameter Test cmd Error info in syslog |
|
@rgarofano-arista please make this configuration vendor specific in case it is required for your platform |
r12f
left a comment
There was a problem hiding this comment.
looks like meter type is vendor specific.
|
@rgarofano-arista can you resolve the conflict? |
96bbcc8 to
cb8dad5
Compare
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
cb8dad5 to
afc14e6
Compare
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
afc14e6 to
4a7fe24
Compare
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
I have changed it so that meter_type is only added to the scheduler command for the th5 asic. |
4a7fe24 to
71059ec
Compare
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]>
71059ec to
70bd85f
Compare
|
@rgarofano-arista PR conflicts with 202511 branch |
|
Manual cherry-pick to 202511 #22071 |
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Priyansh Tratiya <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Saravanan Sellappa <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]>
|
Hi @r12f , could you please approve the PR request to 202412? |
|
@rgarofano-arista could you to submit PR to 202511 and 202412 since cherrypick conflict? |
I already have a PR for 202511 (linked in quoted reply) |
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Yael Tzur <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: ayya <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: nnelluri-cisco <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Raghavendran Ramanathan <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Zhuohui Tan <[email protected]>
…atically (sonic-net#21436) [submodule] Update submodule sonic-utilities to the latest HEAD automatically
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Abhishek <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]>
…c-net#21436)" This reverts commit d474ce8.
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]> Signed-off-by: Ze Gan <[email protected]>
) meter_type is platform specific, so the inclusion of it is only implemented for Broadcom TH5 chip right now. Other chips in the future that require it will need to modify the code. Signed-off-by: Ryan Garofano <[email protected]>
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Packet trimming tests rely on simulating congestion on an egress queue. For this, the tests are trying to apply a shaper that significantly slows down the amount of packets sent out of the target egress queue per second. We found that this shaper doesn't work on th5 with the current config.
How did you do it?
The solution to this is to add
"meter_type" packetswhen creating the blocking scheduler (shaper).How did you verify/test it?
Verified via
tcpdumpthat packet transmission rate was slowed down as expected on th5.Any platform specific information?
This issue was discovered when testing on th5
Supported testbed topology if it's a new test case?
Documentation