[device]: Add SAI checksum verify to TD3 config #8857
Conversation
|
/Azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@theasianpianist Please note that the necessary changes in BRCM SAI is only available in 202012 BRCM SAI 4.3.5.1-3. This means that this PR ideally should wait until the same fix is applied to the master branch BRCM SAI 5.0 before you merge it... |
|
@theasianpianist you should also press BRCM to make sure they push this same BRCM SAI change into their REL_5.0 SUG repo and any future release that they are also developing such as 6.0. They miss this type of things quite often and needs to be reminded unfortunately or else there will be a surprised gap... |
theasianpianist
dismissed
gechiang’s stale review
The base branch was changed.
Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
theasianpianist
force-pushed
the
td3-chksum
branch
from
37cbb82
to
7782ba6
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@theasianpianist , Should this SOC property be applied to all TD3 based HW SKUs or just the two you updated? |
Checked offline with @lguohan, we only need to update the 7050CX3 SKUs |
* [device]: Add SAI checksum verify to TD3 config * A new config option was added to control the value of IPV4_INCR_CHECKSUM_ORIGINAL_VALUE_VERIFY in the EGR_FLEX_CONFIG control register (this prevents checksums of 0xffff from being propagated to other devices)
* [device]: Add SAI checksum verify to TD3 config * A new config option was added to control the value of IPV4_INCR_CHECKSUM_ORIGINAL_VALUE_VERIFY in the EGR_FLEX_CONFIG control register (this prevents checksums of 0xffff from being propagated to other devices)
Related work items: sonic-net#284, sonic-net#288, sonic-net#624, sonic-net#630, sonic-net#640, sonic-net#2164, sonic-net#2206, sonic-net#2207, sonic-net#2233, sonic-net#2234, sonic-net#2238, sonic-net#8857, sonic-net#10034, sonic-net#10519, sonic-net#10685, sonic-net#10711, sonic-net#10987, sonic-net#10990, sonic-net#11047, sonic-net#11070, sonic-net#11117, sonic-net#11186, sonic-net#11207, sonic-net#11213, sonic-net#11215, sonic-net#11220, sonic-net#11221, sonic-net#11257, sonic-net#11291, sonic-net#11298, sonic-net#11301, sonic-net#11326, sonic-net#11333, sonic-net#11335, sonic-net#11341, sonic-net#11344, sonic-net#11347, sonic-net#11359, sonic-net#11366, sonic-net#11368, sonic-net#11370, sonic-net#11372, sonic-net#11375, sonic-net#11385, sonic-net#11386, sonic-net#11394, sonic-net#11397, sonic-net#11401, sonic-net#11402, sonic-net#11403, sonic-net#11405, sonic-net#11414
Signed-off-by: Lawrence Lee lawlee@microsoft.com
Why I did it
A new config option was added to control the value of IPV4_INCR_CHECKSUM_ORIGINAL_VALUE_VERIFY in the EGR_FLEX_CONFIG control register (this prevents checksums of 0xffff from being propagated to other devices)
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
A picture of a cute animal (not mandatory but encouraged)