| .. | .. |
|---|
| 3 | 3 | tristate "Compressed RAM block device support" |
|---|
| 4 | 4 | depends on BLOCK && SYSFS && ZSMALLOC && CRYPTO |
|---|
| 5 | 5 | select CRYPTO_LZO |
|---|
| 6 | | - default n |
|---|
| 7 | 6 | help |
|---|
| 8 | 7 | Creates virtual block devices called /dev/zramX (X = 0, 1, ...). |
|---|
| 9 | 8 | Pages written to these disks are compressed and stored in memory |
|---|
| .. | .. |
|---|
| 13 | 12 | It has several use cases, for example: /tmp storage, use as swap |
|---|
| 14 | 13 | disks and maybe many more. |
|---|
| 15 | 14 | |
|---|
| 16 | | - See Documentation/blockdev/zram.txt for more information. |
|---|
| 15 | + See Documentation/admin-guide/blockdev/zram.rst for more information. |
|---|
| 17 | 16 | |
|---|
| 18 | 17 | config ZRAM_WRITEBACK |
|---|
| 19 | 18 | bool "Write back incompressible or idle page to backing device" |
|---|
| 20 | 19 | depends on ZRAM |
|---|
| 21 | | - default n |
|---|
| 22 | 20 | help |
|---|
| 23 | 21 | With incompressible page, there is no memory saving to keep it |
|---|
| 24 | 22 | in memory. Instead, write it out to backing device. |
|---|
| .. | .. |
|---|
| 28 | 26 | With /sys/block/zramX/{idle,writeback}, application could ask |
|---|
| 29 | 27 | idle page's writeback to the backing device to save in memory. |
|---|
| 30 | 28 | |
|---|
| 31 | | - See Documentation/blockdev/zram.txt for more information. |
|---|
| 29 | + See Documentation/admin-guide/blockdev/zram.rst for more information. |
|---|
| 32 | 30 | |
|---|
| 33 | 31 | config ZRAM_MEMORY_TRACKING |
|---|
| 34 | 32 | bool "Track zRam block status" |
|---|
| .. | .. |
|---|
| 38 | 36 | of zRAM. Admin could see the information via |
|---|
| 39 | 37 | /sys/kernel/debug/zram/zramX/block_state. |
|---|
| 40 | 38 | |
|---|
| 41 | | - See Documentation/blockdev/zram.txt for more information. |
|---|
| 39 | + See Documentation/admin-guide/blockdev/zram.rst for more information. |
|---|