f7a6553933
Why I did it In the bringup of tomahawk4/trident4, we realized that such chips need a larger size of /dev/shm in syncd container, so we added the option --shm-size to the docker create for syncd. The default value for shm-size is 64m; after this change, people can add SYNCD_SHM_SIZE=128m to platform_env.conf to change it to 128m. How to verify it We verified that after this change, 1) on existing platforms without platform_env.conf, the size of /dev/shm in syncd container (df -h | grep shm) is still the default 64M; 2) after we add SYNCD_SHM_SIZE=128m to platform_env.conf, /dev/shm in syncd becomes 128M. |
||
|---|---|---|
| .. | ||
| per_namespace | ||
| share_image | ||
| arp_update_vars.j2 | ||
| buffers_config.j2 | ||
| cbf_config.j2 | ||
| config-chassisdb.service.j2 | ||
| config-setup.service.j2 | ||
| database.service.j2 | ||
| dhcp_relay.service.j2 | ||
| docker_image_ctl.j2 | ||
| iccpd.service.j2 | ||
| init_cfg.json.j2 | ||
| kube_cni.10-flannel.conflist | ||
| lldp.service.j2 | ||
| manifest.json.j2 | ||
| mgmt-framework.service.j2 | ||
| mgmt-framework.timer | ||
| mux.service.j2 | ||
| nat.service.j2 | ||
| organization_extensions.sh | ||
| p4rt.service.j2 | ||
| packages.json.j2 | ||
| pde.service.j2 | ||
| pmon.service.j2 | ||
| qos_config.j2 | ||
| radv.service.j2 | ||
| restapi.service.j2 | ||
| sflow.service.j2 | ||
| snmp.service.j2 | ||
| snmp.timer | ||
| sonic_debian_extension.j2 | ||
| sonic_version.yml.j2 | ||
| sonic-delayed.target | ||
| sonic.target | ||
| swss_vars.j2 | ||
| tacacs-config.service | ||
| tacacs-config.timer | ||
| telemetry.service.j2 | ||
| telemetry.timer | ||
| updategraph.service.j2 | ||