bingwang-ms 84aca00847 [202012]Support different DSCP_TO_TC_MAP for T1 in dualtor deployment (#11580) ... Why I did it This PR is to backport #11569 into 202012 branch. This PR is to apply different DSCP_TO_TC_MAP to downlink and uplink ports on T1 in dualtor deployment. For T1 downlink ports (To T0) The DSCP_TO_TC_MAP is not changed. DSCP2 and DSCP6 are mapped to TC2 and TC6 respectively. For T1 uplink ports (To T1) A new DSCP_TO_TC_MAP|AZURE_UPLINK is defined and applied. DSCP2 and DSCP6 are mapped to TC1 to avoid mixing up lossy and lossless traffic from T2. The extra lossy PG2 and PG6 added in PR #11157 is reverted as well because no traffic from T2 is mapped to PG2 or PG6 now. How I did it Define a new map DSCP_TO_TC_MAP|AZURE_UPLINK for 7260 T1. How to verify it Verified by test case in test_j2files.py.		2022-08-01 08:59:45 -07:00
..
pddf/plugins	[sonic-utilities] Update submodule; Build and install as a Python 3 wheel (#5926)	2020-11-25 10:28:36 -08:00
profiles	[202012]Support different DSCP_TO_TC_MAP for T1 in dualtor deployment (#11580)	2022-08-01 08:59:45 -07:00