Update J2CP QoS test parameters for PR23848#20806
Conversation
The qos parameters for J2C+ asics to reflect the new headroom values.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@vmittal-msft This PR goes alongside your PR over at sonic-net/sonic-buildimage#23848 Who can we ask to review these PRs? My changes should only go in when yours merges as well. We will want both changes to buildimage and mgmt backported to MSFT 202503 too |
| pkts_num_trig_pfc: 764336 | ||
| pkts_num_trig_ingr_drp: 765653 | ||
| pkts_num_trig_pfc: 762403 | ||
| pkts_num_trig_ingr_drp: 775751 |
There was a problem hiding this comment.
400000 30m 0 2560 1495040 -5 1454025
Based on above pg limits for 400g/30m, total space a pg should get is shared space + per pg headroom limit. so i believe the ingress drop should happen with more than 1.5 MB space occupied ( per pg limit - 1.5mb & shared space) but about no is 775kb which seems less to me. Can you please double check ?
There was a problem hiding this comment.
Thank you for reviewing, Vineet
1495040 bytes is the headroom space for this profile
775751 - 762403 = 13348 packets to fill the headroom
13348 * 112 = 1494976 bytes, the margin and dynamic accounting in the test then accounts for the < 1 packet difference between 1494976 and 1495040
Let me know if that clarifies. Thanks again
vmittal-msft
left a comment
There was a problem hiding this comment.
Please see comment.it should be applicable to rest of the places as well.
|
@ansrajpu-git @saksarav-nokia to review as well. |
|
@peterbailey-arista, there is a cherry-pick conflict for 202503 branch. Please create a PR in the ,msft/202503 directly |
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values.
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values.
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: selldinesh <dinesh.sellappan@keysight.com>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values.
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: Saravanan <saravanan@nexthop.ai>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values.
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: YiFan Wang <yifan@nexthop.ai>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: Lakshmi Yarramaneni <lakshmi@nexthop.ai>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values.
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values. Signed-off-by: Yael Tzur <ytzur@nvidia.com>
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values.
What is the motivation for this PR? How did you do it? An increased packet size was needed for the hdrm_pool_size tests so fewer packets would be needed - the test was too slow prior to the change and prone to timing out. pkts_num_trig_pfc, pkts_num_trig_ingr_drp, pkts_num_hdrm_full were recalculated for the new headroom size How did you verify/test it? Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values.
These qos parameters are needed for J2C+ asics to reflect the new headroom values introduced in
sonic-net/sonic-buildimage#23848
This change should only merge after PR23848 does
Both changes must be backported to MSFT-202503 as well.
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Testing was done on msft-202503 with J2C+ hardware to verify the sonic-mgmt tests pass where the previously failed with the new headroom values.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation