Skip to content

Commit

Permalink
defconfig: Disable zram writeback
Browse files Browse the repository at this point in the history
- 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 <togofire@mailfence.com>
Change-Id: I2c5a4fe31dc358dc48fa4d9534dfe50d58d30afb
  • Loading branch information
TogoFire committed May 24, 2023
1 parent 090cf20 commit ac51d53
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion arch/arm64/configs/daisy_defconfig
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit ac51d53

Please sign in to comment.