matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
e15acb59ff
sonic-buildimage/device/mellanox/x86_64-mlnx_msn3800-r0/Mellanox-SN3800-D112C8/buffers_defaults_t1.j2

24 lines
1.0 KiB
Plaintext
Raw Normal View History

Support single ingress pool for MSFT SKUs and optimize headroom calculation (#4686) Calculate pool size in t1 as 24 * downlink port + 8 * uplink port - Take both port and peer MTU into account when calculating headroom - Worst case factor is decreased to 50% - Mellanox-SN2700-C28D8 t0, assume 48 * 50G/5m + 8 * 100G/40m ports - Mellanox-SN2700 (C32) - t0: 16 * 100G/5m + 16 * 100G/40m - t1: 16 * 100G/40m + 16 * 100G/300m Signed-off-by: Stephen Sun <stephens@mellanox.com> Co-authored-by: Stephen Sun <stephens@mellanox.com>
2020-08-13 05:12:09 -05:00
{% set default_cable = '5m' %}
Support shared headroom pool for Microsoft SKUs (#6366) - Why I did it Support shared headroom pool Signed-off-by: Stephen Sun stephens@nvidia.com - How I did it Port configurations for SKUs based on 2700/3800 platform from 201911 For SN3800 platform: C64: 32 100G down links and 32 100G up links. D112C8: 112 50G down links and 8 100G up links. D24C52: 24 50G down links, 20 100G down links, and 32 100G up links. D28C50: 28 50G down links, 18 100G down links, and 32 100G up links. For SN2700 platform: D48C8: 48 50G down links and 8 100G up links C32: 16 100G downlinks and 16 100G uplinks Add configuration for Mellanox-SN4600C-D112C8 112 50G down links and 8 100G up links. - How to verify it Run regression test.
2021-02-16 10:53:40 -06:00
{% set ingress_lossless_pool_size = '19124224' %}
{% set ingress_lossless_pool_xoff = '4333568' %}
Support single ingress pool for MSFT SKUs and optimize headroom calculation (#4686) Calculate pool size in t1 as 24 * downlink port + 8 * uplink port - Take both port and peer MTU into account when calculating headroom - Worst case factor is decreased to 50% - Mellanox-SN2700-C28D8 t0, assume 48 * 50G/5m + 8 * 100G/40m ports - Mellanox-SN2700 (C32) - t0: 16 * 100G/5m + 16 * 100G/40m - t1: 16 * 100G/40m + 16 * 100G/300m Signed-off-by: Stephen Sun <stephens@mellanox.com> Co-authored-by: Stephen Sun <stephens@mellanox.com>
2020-08-13 05:12:09 -05:00
{% set egress_lossless_pool_size = '34287552' %}
Support shared headroom pool for Microsoft SKUs (#6366) - Why I did it Support shared headroom pool Signed-off-by: Stephen Sun stephens@nvidia.com - How I did it Port configurations for SKUs based on 2700/3800 platform from 201911 For SN3800 platform: C64: 32 100G down links and 32 100G up links. D112C8: 112 50G down links and 8 100G up links. D24C52: 24 50G down links, 20 100G down links, and 32 100G up links. D28C50: 28 50G down links, 18 100G down links, and 32 100G up links. For SN2700 platform: D48C8: 48 50G down links and 8 100G up links C32: 16 100G downlinks and 16 100G uplinks Add configuration for Mellanox-SN4600C-D112C8 112 50G down links and 8 100G up links. - How to verify it Run regression test.
2021-02-16 10:53:40 -06:00
{% set egress_lossy_pool_size = '19124224' %}
Support single ingress pool for MSFT SKUs and optimize headroom calculation (#4686) Calculate pool size in t1 as 24 * downlink port + 8 * uplink port - Take both port and peer MTU into account when calculating headroom - Worst case factor is decreased to 50% - Mellanox-SN2700-C28D8 t0, assume 48 * 50G/5m + 8 * 100G/40m ports - Mellanox-SN2700 (C32) - t0: 16 * 100G/5m + 16 * 100G/40m - t1: 16 * 100G/40m + 16 * 100G/300m Signed-off-by: Stephen Sun <stephens@mellanox.com> Co-authored-by: Stephen Sun <stephens@mellanox.com>
2020-08-13 05:12:09 -05:00
[Reclaim buffer][202012] Reclaim unused buffers by applying zero buffer profiles (#9063) - Why I did it Support zero buffer profiles 1. Add buffer profiles and pool definition for zero buffer profiles 2. Support applying zero profiles on INACTIVE PORTS 3. Enable dynamic buffer manager to load zero pools and profiles from a JSON file - How I did it Add buffer profiles and pool definition for zero buffer profiles If the buffer model is static: * Apply normal buffer profiles to admin-up ports * Apply zero buffer profiles to admin-down ports If the buffer model is dynamic: * Apply normal buffer profiles to all ports * buffer manager will take care when a port is shut down Update buffers_config.j2 to support INACTIVE PORTS by extending the existing macros to generate the various buffer objects, including PGs, queues, ingress/egress profile lists Originally, all the macros to generate the above buffer objects took active ports only as an argument. Now that buffer items need to be generated on inactive ports as well, an extra argument representing the inactive ports need to be added. To be backward compatible, a new series of macros are introduced to take both active and inactive ports as arguments The original version (with active ports only) will be checked first. If it is not defined, then the extended version will be called. Only vendors who support zero profiles need to change their buffer templates Enable buffer manager to load zero pools and profiles from a JSON file: The JSON file is provided on a per-platform basis It is copied from platform/<vendor> folder to /usr/share/sonic/temlates folder in compiling time and rendered when the swss container is being created. To make code clean and reduce redundant code, extract common macros from buffer_defaults_t{0,1}.j2 of all SKUs to two common files: One in Mellanox-SN2700-D48C8 for single ingress pool mode The other in ACS-MSN2700 for double ingress pool mode Those files of all other SKUs will be symbol link to the above files Update sonic-cfggen test accordingly: * Adjust example output file of JSON template for unit test * Add unit test in for Mellanox's new buffer templates. - How to verify it Regression test. Unit test in sonic-cfggen Run regression test and manually test. Signed-off-by: stephens <stephens@nvidia.com>
2021-12-09 09:34:56 -06:00
{% import 'buffers_defaults_objects.j2' as defs with context %}
Support single ingress pool for MSFT SKUs and optimize headroom calculation (#4686) Calculate pool size in t1 as 24 * downlink port + 8 * uplink port - Take both port and peer MTU into account when calculating headroom - Worst case factor is decreased to 50% - Mellanox-SN2700-C28D8 t0, assume 48 * 50G/5m + 8 * 100G/40m ports - Mellanox-SN2700 (C32) - t0: 16 * 100G/5m + 16 * 100G/40m - t1: 16 * 100G/40m + 16 * 100G/300m Signed-off-by: Stephen Sun <stephens@mellanox.com> Co-authored-by: Stephen Sun <stephens@mellanox.com>
2020-08-13 05:12:09 -05:00
[Reclaim buffer][202012] Reclaim unused buffers by applying zero buffer profiles (#9063) - Why I did it Support zero buffer profiles 1. Add buffer profiles and pool definition for zero buffer profiles 2. Support applying zero profiles on INACTIVE PORTS 3. Enable dynamic buffer manager to load zero pools and profiles from a JSON file - How I did it Add buffer profiles and pool definition for zero buffer profiles If the buffer model is static: * Apply normal buffer profiles to admin-up ports * Apply zero buffer profiles to admin-down ports If the buffer model is dynamic: * Apply normal buffer profiles to all ports * buffer manager will take care when a port is shut down Update buffers_config.j2 to support INACTIVE PORTS by extending the existing macros to generate the various buffer objects, including PGs, queues, ingress/egress profile lists Originally, all the macros to generate the above buffer objects took active ports only as an argument. Now that buffer items need to be generated on inactive ports as well, an extra argument representing the inactive ports need to be added. To be backward compatible, a new series of macros are introduced to take both active and inactive ports as arguments The original version (with active ports only) will be checked first. If it is not defined, then the extended version will be called. Only vendors who support zero profiles need to change their buffer templates Enable buffer manager to load zero pools and profiles from a JSON file: The JSON file is provided on a per-platform basis It is copied from platform/<vendor> folder to /usr/share/sonic/temlates folder in compiling time and rendered when the swss container is being created. To make code clean and reduce redundant code, extract common macros from buffer_defaults_t{0,1}.j2 of all SKUs to two common files: One in Mellanox-SN2700-D48C8 for single ingress pool mode The other in ACS-MSN2700 for double ingress pool mode Those files of all other SKUs will be symbol link to the above files Update sonic-cfggen test accordingly: * Adjust example output file of JSON template for unit test * Add unit test in for Mellanox's new buffer templates. - How to verify it Regression test. Unit test in sonic-cfggen Run regression test and manually test. Signed-off-by: stephens <stephens@nvidia.com>
2021-12-09 09:34:56 -06:00
{%- macro generate_buffer_pool_and_profiles_with_inactive_ports(port_names_inactive) %}
{{ defs.generate_buffer_pool_and_profiles_with_inactive_ports(port_names_inactive) }}
Support single ingress pool for MSFT SKUs and optimize headroom calculation (#4686) Calculate pool size in t1 as 24 * downlink port + 8 * uplink port - Take both port and peer MTU into account when calculating headroom - Worst case factor is decreased to 50% - Mellanox-SN2700-C28D8 t0, assume 48 * 50G/5m + 8 * 100G/40m ports - Mellanox-SN2700 (C32) - t0: 16 * 100G/5m + 16 * 100G/40m - t1: 16 * 100G/40m + 16 * 100G/300m Signed-off-by: Stephen Sun <stephens@mellanox.com> Co-authored-by: Stephen Sun <stephens@mellanox.com>
2020-08-13 05:12:09 -05:00
{%- endmacro %}
[Reclaim buffer][202012] Reclaim unused buffers by applying zero buffer profiles (#9063) - Why I did it Support zero buffer profiles 1. Add buffer profiles and pool definition for zero buffer profiles 2. Support applying zero profiles on INACTIVE PORTS 3. Enable dynamic buffer manager to load zero pools and profiles from a JSON file - How I did it Add buffer profiles and pool definition for zero buffer profiles If the buffer model is static: * Apply normal buffer profiles to admin-up ports * Apply zero buffer profiles to admin-down ports If the buffer model is dynamic: * Apply normal buffer profiles to all ports * buffer manager will take care when a port is shut down Update buffers_config.j2 to support INACTIVE PORTS by extending the existing macros to generate the various buffer objects, including PGs, queues, ingress/egress profile lists Originally, all the macros to generate the above buffer objects took active ports only as an argument. Now that buffer items need to be generated on inactive ports as well, an extra argument representing the inactive ports need to be added. To be backward compatible, a new series of macros are introduced to take both active and inactive ports as arguments The original version (with active ports only) will be checked first. If it is not defined, then the extended version will be called. Only vendors who support zero profiles need to change their buffer templates Enable buffer manager to load zero pools and profiles from a JSON file: The JSON file is provided on a per-platform basis It is copied from platform/<vendor> folder to /usr/share/sonic/temlates folder in compiling time and rendered when the swss container is being created. To make code clean and reduce redundant code, extract common macros from buffer_defaults_t{0,1}.j2 of all SKUs to two common files: One in Mellanox-SN2700-D48C8 for single ingress pool mode The other in ACS-MSN2700 for double ingress pool mode Those files of all other SKUs will be symbol link to the above files Update sonic-cfggen test accordingly: * Adjust example output file of JSON template for unit test * Add unit test in for Mellanox's new buffer templates. - How to verify it Regression test. Unit test in sonic-cfggen Run regression test and manually test. Signed-off-by: stephens <stephens@nvidia.com>
2021-12-09 09:34:56 -06:00
{%- macro generate_profile_lists_with_inactive_ports(port_names_active, port_names_inactive) %}
{{ defs.generate_profile_lists(port_names_active, port_names_inactive) }}
Support single ingress pool for MSFT SKUs and optimize headroom calculation (#4686) Calculate pool size in t1 as 24 * downlink port + 8 * uplink port - Take both port and peer MTU into account when calculating headroom - Worst case factor is decreased to 50% - Mellanox-SN2700-C28D8 t0, assume 48 * 50G/5m + 8 * 100G/40m ports - Mellanox-SN2700 (C32) - t0: 16 * 100G/5m + 16 * 100G/40m - t1: 16 * 100G/40m + 16 * 100G/300m Signed-off-by: Stephen Sun <stephens@mellanox.com> Co-authored-by: Stephen Sun <stephens@mellanox.com>
2020-08-13 05:12:09 -05:00
{%- endmacro %}
[Reclaim buffer][202012] Reclaim unused buffers by applying zero buffer profiles (#9063) - Why I did it Support zero buffer profiles 1. Add buffer profiles and pool definition for zero buffer profiles 2. Support applying zero profiles on INACTIVE PORTS 3. Enable dynamic buffer manager to load zero pools and profiles from a JSON file - How I did it Add buffer profiles and pool definition for zero buffer profiles If the buffer model is static: * Apply normal buffer profiles to admin-up ports * Apply zero buffer profiles to admin-down ports If the buffer model is dynamic: * Apply normal buffer profiles to all ports * buffer manager will take care when a port is shut down Update buffers_config.j2 to support INACTIVE PORTS by extending the existing macros to generate the various buffer objects, including PGs, queues, ingress/egress profile lists Originally, all the macros to generate the above buffer objects took active ports only as an argument. Now that buffer items need to be generated on inactive ports as well, an extra argument representing the inactive ports need to be added. To be backward compatible, a new series of macros are introduced to take both active and inactive ports as arguments The original version (with active ports only) will be checked first. If it is not defined, then the extended version will be called. Only vendors who support zero profiles need to change their buffer templates Enable buffer manager to load zero pools and profiles from a JSON file: The JSON file is provided on a per-platform basis It is copied from platform/<vendor> folder to /usr/share/sonic/temlates folder in compiling time and rendered when the swss container is being created. To make code clean and reduce redundant code, extract common macros from buffer_defaults_t{0,1}.j2 of all SKUs to two common files: One in Mellanox-SN2700-D48C8 for single ingress pool mode The other in ACS-MSN2700 for double ingress pool mode Those files of all other SKUs will be symbol link to the above files Update sonic-cfggen test accordingly: * Adjust example output file of JSON template for unit test * Add unit test in for Mellanox's new buffer templates. - How to verify it Regression test. Unit test in sonic-cfggen Run regression test and manually test. Signed-off-by: stephens <stephens@nvidia.com>
2021-12-09 09:34:56 -06:00
{%- macro generate_queue_buffers_with_inactive_ports(port_names_active, port_names_inactive) %}
{{ defs.generate_queue_buffers(port_names_active, port_names_inactive) }}
{%- endmacro %}
Support single ingress pool for MSFT SKUs and optimize headroom calculation (#4686) Calculate pool size in t1 as 24 * downlink port + 8 * uplink port - Take both port and peer MTU into account when calculating headroom - Worst case factor is decreased to 50% - Mellanox-SN2700-C28D8 t0, assume 48 * 50G/5m + 8 * 100G/40m ports - Mellanox-SN2700 (C32) - t0: 16 * 100G/5m + 16 * 100G/40m - t1: 16 * 100G/40m + 16 * 100G/300m Signed-off-by: Stephen Sun <stephens@mellanox.com> Co-authored-by: Stephen Sun <stephens@mellanox.com>
2020-08-13 05:12:09 -05:00
[Reclaim buffer][202012] Reclaim unused buffers by applying zero buffer profiles (#9063) - Why I did it Support zero buffer profiles 1. Add buffer profiles and pool definition for zero buffer profiles 2. Support applying zero profiles on INACTIVE PORTS 3. Enable dynamic buffer manager to load zero pools and profiles from a JSON file - How I did it Add buffer profiles and pool definition for zero buffer profiles If the buffer model is static: * Apply normal buffer profiles to admin-up ports * Apply zero buffer profiles to admin-down ports If the buffer model is dynamic: * Apply normal buffer profiles to all ports * buffer manager will take care when a port is shut down Update buffers_config.j2 to support INACTIVE PORTS by extending the existing macros to generate the various buffer objects, including PGs, queues, ingress/egress profile lists Originally, all the macros to generate the above buffer objects took active ports only as an argument. Now that buffer items need to be generated on inactive ports as well, an extra argument representing the inactive ports need to be added. To be backward compatible, a new series of macros are introduced to take both active and inactive ports as arguments The original version (with active ports only) will be checked first. If it is not defined, then the extended version will be called. Only vendors who support zero profiles need to change their buffer templates Enable buffer manager to load zero pools and profiles from a JSON file: The JSON file is provided on a per-platform basis It is copied from platform/<vendor> folder to /usr/share/sonic/temlates folder in compiling time and rendered when the swss container is being created. To make code clean and reduce redundant code, extract common macros from buffer_defaults_t{0,1}.j2 of all SKUs to two common files: One in Mellanox-SN2700-D48C8 for single ingress pool mode The other in ACS-MSN2700 for double ingress pool mode Those files of all other SKUs will be symbol link to the above files Update sonic-cfggen test accordingly: * Adjust example output file of JSON template for unit test * Add unit test in for Mellanox's new buffer templates. - How to verify it Regression test. Unit test in sonic-cfggen Run regression test and manually test. Signed-off-by: stephens <stephens@nvidia.com>
2021-12-09 09:34:56 -06:00
{%- macro generate_pg_profiles_with_inactive_ports(port_names_active, port_names_inactive) %}
{{ defs.generate_pg_profiles(port_names_active, port_names_inactive) }}
Support single ingress pool for MSFT SKUs and optimize headroom calculation (#4686) Calculate pool size in t1 as 24 * downlink port + 8 * uplink port - Take both port and peer MTU into account when calculating headroom - Worst case factor is decreased to 50% - Mellanox-SN2700-C28D8 t0, assume 48 * 50G/5m + 8 * 100G/40m ports - Mellanox-SN2700 (C32) - t0: 16 * 100G/5m + 16 * 100G/40m - t1: 16 * 100G/40m + 16 * 100G/300m Signed-off-by: Stephen Sun <stephens@mellanox.com> Co-authored-by: Stephen Sun <stephens@mellanox.com>
2020-08-13 05:12:09 -05:00
{%- endmacro %}
Reference in New Issue Copy Permalink