Let's enable ZRAM with 2G. Should help prevent peak OOM scenarios.
For more info see: https://www.kernel.org/doc/html/latest/admin-guide/blockdev/zram.html
Reviewed-by: Eric Engestrom <eric@igalia.com>
Signed-off-by: David Heidelberg <david.heidelberg@collabora.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19535>
echo -n $HWCI_KERNEL_MODULES | xargs -d, -n1 /usr/sbin/modprobe
}
+# Set up ZRAM
+HWCI_ZRAM_SIZE=2G
+if zramctl --find --size $HWCI_ZRAM_SIZE -a zstd; then
+ mkswap /dev/zram0
+ swapon /dev/zram0
+ echo "zram: $HWCI_ZRAM_SIZE activated"
+else
+ echo "zram: skipping, not supported"
+fi
+
#
# Load the KVM module specific to the detected CPU virtualization extensions:
# - vmx for Intel VT
CONFIG_LOCALVERSION_AUTO=y
CONFIG_DEBUG_KERNEL=y
+CONFIG_CRYPTO_ZSTD=y
+CONFIG_ZRAM_MEMORY_TRACKING=y
+CONFIG_ZRAM_WRITEBACK=y
+CONFIG_ZRAM=y
+CONFIG_ZSMALLOC_STAT=y
+
# abootimg with a 'dummy' rootfs fails with root=/dev/nfs
CONFIG_BLK_DEV_INITRD=n
CONFIG_LOCALVERSION_AUTO=y
CONFIG_DEBUG_KERNEL=y
+CONFIG_CRYPTO_ZSTD=y
+CONFIG_ZRAM_MEMORY_TRACKING=y
+CONFIG_ZRAM_WRITEBACK=y
+CONFIG_ZRAM=y
+CONFIG_ZSMALLOC_STAT=y
+
# abootimg with a 'dummy' rootfs fails with root=/dev/nfs
CONFIG_BLK_DEV_INITRD=n
CONFIG_LOCALVERSION_AUTO=y
CONFIG_DEBUG_KERNEL=y
+CONFIG_CRYPTO_ZSTD=y
+CONFIG_ZRAM_MEMORY_TRACKING=y
+CONFIG_ZRAM_WRITEBACK=y
+CONFIG_ZRAM=y
+CONFIG_ZSMALLOC_STAT=y
+
CONFIG_PWM=y
CONFIG_PM_DEVFREQ=y
CONFIG_OF=y
variables:
DEBIAN_X86_BUILD_BASE_IMAGE: "debian/x86_build-base"
- DEBIAN_BASE_TAG: "2022-11-26-use-meson-env2mfile"
+ DEBIAN_BASE_TAG: "2022-12-02-kernel-zram"
DEBIAN_X86_BUILD_IMAGE_PATH: "debian/x86_build"
DEBIAN_BUILD_TAG: "2022-11-03-ci-fairy-s3"
ALPINE_X86_BUILD_TAG: "2022-11-28-disable-mold"
FEDORA_X86_BUILD_TAG: "2022-09-22-python3-ply-2"
- KERNEL_ROOTFS_TAG: "2022-11-17-weston"
+ KERNEL_ROOTFS_TAG: "2022-12-02-kernel-zram"
WINDOWS_X64_VS_PATH: "windows/x64_vs"
WINDOWS_X64_VS_TAG: "2022-10-20-upgrade-zlib"