sonic-buildimage/files/initramfs-tools/modules

squashfs
overlay
vfat
nls_ascii
nls_cp437
nls_utf8
nvme
zstd
New release v1.0.0 2016-03-08 13:42:20 -06:00			`squashfs`
[baseimage]: build root filesystem via overlay fs instead of aufs 2017-09-02 17:32:31 -05:00			`overlay`
[Arista]: Add VFAT support in initramfs (#208) 2017-01-24 21:18:01 -06:00			`vfat`
[device]: Enable arista drivers for sonic-linux-kernel 4.9 (#21) * Enable arista drivers * Add vfat ascii charset in initramfs * Update boot0.j2 for 4.9 kernel * Fix i2c offsets in sensors.conf * Bump sonic-platform-modules-arista submodule 2018-03-27 11:32:05 -05:00			`nls_ascii`
[Arista]: Add VFAT support in initramfs (#208) 2017-01-24 21:18:01 -06:00			`nls_cp437`
			`nls_utf8`
[NVMe] Add NVMe SSD disc type support to installer.sh script (#6142) In order to install a SONiC image on top of a NVMe SSD disc properly with ONIE we must configure it properly on the installer.sh script. Signed-off-by: Shlomi Bitton <shlomibi@nvidia.com> 2020-12-09 21:03:27 -06:00			`nvme`
Add optional zram compression for docker_inram Some devices running SONiC have a small storage device (2G and 4G mainly) The SONiC image growth over time has made it impossible to install 2 images on a single device. Some mitigations have been implemented in the past for some devices but there is a need to do more. One such mitigation is `docker_inram` which creates a `tmpfs` and extracts `dockerfs.tar.gz` in it. This all happens in the SONiC initramfs and by ensuring the installation process does not extract `dockerfs.tar.gz` on the flash but keep the file as is. This mitigation does a tradeoff by using more RAM to reduce the disk footprint. It however creates new issues for devices with 4G of system memory since the extracted `dockerfs.tar.gz` nears the 1.6G. Considering debian upgrades (with dual base images) and the continuous stream of features this is only going to get bigger. This change introduces an alternative to the `tmpfs` by allowing a system to extract the `dockerfs.tar.gz` inside a `zram` device thus bringing compression in play at the detriment of performance. Introduce 2 new optional kernel parameters to be consumed by SONiC initramfs. - `docker_inram_size` which represent the max physical size of the `zram` or `tmpfs` volume (defaults to DOCKER_RAMFS_SIZE) - `docker_inram_algo` which is the method to use to extract the `dockerfs.tar.gz` (defaults to `tmpfs`) other values are considered to be compression algorithm for `zram` (e.g `zstd`, `zlo-rle`, `lz4`) Refactored the logic to mount the docker fs in the SONiC initramfs under the `union-mount` script. Moved the code into a function to make it cleaner and separated the inram volume creation and docker extraction. On Arista platform with a flash smaller or equal to 4GB set `docker_inram_algo` to `zstd` which produces the best compression ratio at the detriment of a slower write performance and a similar read performance to other `zram` compression algorithms. 2023-05-11 04:46:36 -05:00			`zstd`