From ac51d531068f78b2892ee8c285c8803a9c0cfd75 Mon Sep 17 00:00:00 2001 From: TogoFire Date: Sat, 20 May 2023 13:39:08 -0300 Subject: [PATCH] defconfig: Disable zram writeback - Disable this, as it can cause 100% zram usage - By the way, Zram writeback is officially useless, Arter has disabled it - ZRAM WRITEBACK can sometimes be bad because it may cause system freezes or crashes. This happens when the compressed data in ZRAM exceeds its upper limit, causing the system to try to move the excess data to swap space. If writeback is enabled and the swap space is already full, the system may become unresponsive or crash altogether. Additionally, if ZRAM is being used on a system with low memory, enabling writeback may consume more memory than is available, leading to performance issues. Overall, while ZRAM can provide benefits in terms of reducing memory usage, enabling writeback should be done with caution and only on systems with sufficient swap space and memory. Signed-off-by: TogoFire Change-Id: I2c5a4fe31dc358dc48fa4d9534dfe50d58d30afb --- arch/arm64/configs/daisy_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/configs/daisy_defconfig b/arch/arm64/configs/daisy_defconfig index 262924b4155c..d6f2447cd42a 100644 --- a/arch/arm64/configs/daisy_defconfig +++ b/arch/arm64/configs/daisy_defconfig @@ -1283,7 +1283,7 @@ CONFIG_BLK_DEV=y # CONFIG_BLK_DEV_NULL_BLK is not set CONFIG_ZRAM=y CONFIG_ZRAM_DEFAULT_COMP_ALGORITHM="zstd" -CONFIG_ZRAM_WRITEBACK=y +# CONFIG_ZRAM_WRITEBACK is not set # CONFIG_ZRAM_MEMORY_TRACKING is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y