161 lines · plain
1What: /sys/block/zram<id>/disksize2Date: August 20103Contact: Nitin Gupta <ngupta@vflare.org>4Description:5 The disksize file is read-write and specifies the disk size6 which represents the limit on the *uncompressed* worth of data7 that can be stored in this disk.8 Unit: bytes9 10What: /sys/block/zram<id>/initstate11Date: August 201012Contact: Nitin Gupta <ngupta@vflare.org>13Description:14 The initstate file is read-only and shows the initialization15 state of the device.16 17What: /sys/block/zram<id>/reset18Date: August 201019Contact: Nitin Gupta <ngupta@vflare.org>20Description:21 The reset file is write-only and allows resetting the22 device. The reset operation frees all the memory associated23 with this device.24 25What: /sys/block/zram<id>/max_comp_streams26Date: February 201427Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>28Description:29 The max_comp_streams file is read-write and specifies the30 number of backend's zcomp_strm compression streams (number of31 concurrent compress operations).32 33What: /sys/block/zram<id>/comp_algorithm34Date: February 201435Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>36Description:37 The comp_algorithm file is read-write and lets to show38 available and selected compression algorithms, change39 compression algorithm selection.40 41What: /sys/block/zram<id>/mem_used_max42Date: August 201443Contact: Minchan Kim <minchan@kernel.org>44Description:45 The mem_used_max file is write-only and is used to reset46 the counter of maximum memory zram have consumed to store47 compressed data. For resetting the value, you should write48 "0". Otherwise, you could see -EINVAL.49 Unit: bytes50 51What: /sys/block/zram<id>/mem_limit52Date: August 201453Contact: Minchan Kim <minchan@kernel.org>54Description:55 The mem_limit file is write-only and specifies the maximum56 amount of memory ZRAM can use to store the compressed data.57 The limit could be changed in run time and "0" means disable58 the limit. No limit is the initial state. Unit: bytes59 60What: /sys/block/zram<id>/compact61Date: August 201562Contact: Minchan Kim <minchan@kernel.org>63Description:64 The compact file is write-only and trigger compaction for65 allocator zrm uses. The allocator moves some objects so that66 it could free fragment space.67 68What: /sys/block/zram<id>/io_stat69Date: August 201570Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>71Description:72 The io_stat file is read-only and accumulates device's I/O73 statistics not accounted by block layer. For example,74 failed_reads, failed_writes, etc. File format is similar to75 block layer statistics file format.76 77What: /sys/block/zram<id>/mm_stat78Date: August 201579Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>80Description:81 The mm_stat file is read-only and represents device's mm82 statistics (orig_data_size, compr_data_size, etc.) in a format83 similar to block layer statistics file format.84 85What: /sys/block/zram<id>/debug_stat86Date: July 201687Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>88Description:89 The debug_stat file is read-only and represents various90 device's debugging info useful for kernel developers. Its91 format is not documented intentionally and may change92 anytime without any notice.93 94What: /sys/block/zram<id>/backing_dev95Date: June 201796Contact: Minchan Kim <minchan@kernel.org>97Description:98 The backing_dev file is read-write and set up backing99 device for zram to write incompressible pages.100 For using, user should enable CONFIG_ZRAM_WRITEBACK.101 102What: /sys/block/zram<id>/idle103Date: November 2018104Contact: Minchan Kim <minchan@kernel.org>105Description:106 idle file is write-only and mark zram slot as idle.107 If system has mounted debugfs, user can see which slots108 are idle via /sys/kernel/debug/zram/zram<id>/block_state109 110What: /sys/block/zram<id>/writeback111Date: November 2018112Contact: Minchan Kim <minchan@kernel.org>113Description:114 The writeback file is write-only and trigger idle and/or115 huge page writeback to backing device.116 117What: /sys/block/zram<id>/bd_stat118Date: November 2018119Contact: Minchan Kim <minchan@kernel.org>120Description:121 The bd_stat file is read-only and represents backing device's122 statistics (bd_count, bd_reads, bd_writes) in a format123 similar to block layer statistics file format.124 125What: /sys/block/zram<id>/writeback_limit_enable126Date: November 2018127Contact: Minchan Kim <minchan@kernel.org>128Description:129 The writeback_limit_enable file is read-write and specifies130 eanbe of writeback_limit feature. "1" means eable the feature.131 No limit "0" is the initial state.132 133What: /sys/block/zram<id>/writeback_limit134Date: November 2018135Contact: Minchan Kim <minchan@kernel.org>136Description:137 The writeback_limit file is read-write and specifies the maximum138 amount of writeback ZRAM can do. The limit could be changed139 in run time.140 141What: /sys/block/zram<id>/recomp_algorithm142Date: November 2022143Contact: Sergey Senozhatsky <senozhatsky@chromium.org>144Description:145 The recomp_algorithm file is read-write and allows to set146 or show secondary compression algorithms.147 148What: /sys/block/zram<id>/recompress149Date: November 2022150Contact: Sergey Senozhatsky <senozhatsky@chromium.org>151Description:152 The recompress file is write-only and triggers re-compression153 with secondary compression algorithms.154 155What: /sys/block/zram<id>/algorithm_params156Date: August 2024157Contact: Sergey Senozhatsky <senozhatsky@chromium.org>158Description:159 The algorithm_params file is write-only and is used to setup160 compression algorithm parameters.161