0001 What: /sys/block/zram<id>/disksize
0002 Date: August 2010
0003 Contact: Nitin Gupta <ngupta@vflare.org>
0004 Description:
0005 The disksize file is read-write and specifies the disk size
0006 which represents the limit on the *uncompressed* worth of data
0007 that can be stored in this disk.
0008 Unit: bytes
0009
0010 What: /sys/block/zram<id>/initstate
0011 Date: August 2010
0012 Contact: Nitin Gupta <ngupta@vflare.org>
0013 Description:
0014 The initstate file is read-only and shows the initialization
0015 state of the device.
0016
0017 What: /sys/block/zram<id>/reset
0018 Date: August 2010
0019 Contact: Nitin Gupta <ngupta@vflare.org>
0020 Description:
0021 The reset file is write-only and allows resetting the
0022 device. The reset operation frees all the memory associated
0023 with this device.
0024
0025 What: /sys/block/zram<id>/max_comp_streams
0026 Date: February 2014
0027 Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
0028 Description:
0029 The max_comp_streams file is read-write and specifies the
0030 number of backend's zcomp_strm compression streams (number of
0031 concurrent compress operations).
0032
0033 What: /sys/block/zram<id>/comp_algorithm
0034 Date: February 2014
0035 Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
0036 Description:
0037 The comp_algorithm file is read-write and lets to show
0038 available and selected compression algorithms, change
0039 compression algorithm selection.
0040
0041 What: /sys/block/zram<id>/mem_used_max
0042 Date: August 2014
0043 Contact: Minchan Kim <minchan@kernel.org>
0044 Description:
0045 The mem_used_max file is write-only and is used to reset
0046 the counter of maximum memory zram have consumed to store
0047 compressed data. For resetting the value, you should write
0048 "0". Otherwise, you could see -EINVAL.
0049 Unit: bytes
0050
0051 What: /sys/block/zram<id>/mem_limit
0052 Date: August 2014
0053 Contact: Minchan Kim <minchan@kernel.org>
0054 Description:
0055 The mem_limit file is write-only and specifies the maximum
0056 amount of memory ZRAM can use to store the compressed data.
0057 The limit could be changed in run time and "0" means disable
0058 the limit. No limit is the initial state. Unit: bytes
0059
0060 What: /sys/block/zram<id>/compact
0061 Date: August 2015
0062 Contact: Minchan Kim <minchan@kernel.org>
0063 Description:
0064 The compact file is write-only and trigger compaction for
0065 allocator zrm uses. The allocator moves some objects so that
0066 it could free fragment space.
0067
0068 What: /sys/block/zram<id>/io_stat
0069 Date: August 2015
0070 Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
0071 Description:
0072 The io_stat file is read-only and accumulates device's I/O
0073 statistics not accounted by block layer. For example,
0074 failed_reads, failed_writes, etc. File format is similar to
0075 block layer statistics file format.
0076
0077 What: /sys/block/zram<id>/mm_stat
0078 Date: August 2015
0079 Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
0080 Description:
0081 The mm_stat file is read-only and represents device's mm
0082 statistics (orig_data_size, compr_data_size, etc.) in a format
0083 similar to block layer statistics file format.
0084
0085 What: /sys/block/zram<id>/debug_stat
0086 Date: July 2016
0087 Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
0088 Description:
0089 The debug_stat file is read-only and represents various
0090 device's debugging info useful for kernel developers. Its
0091 format is not documented intentionally and may change
0092 anytime without any notice.
0093
0094 What: /sys/block/zram<id>/backing_dev
0095 Date: June 2017
0096 Contact: Minchan Kim <minchan@kernel.org>
0097 Description:
0098 The backing_dev file is read-write and set up backing
0099 device for zram to write incompressible pages.
0100 For using, user should enable CONFIG_ZRAM_WRITEBACK.
0101
0102 What: /sys/block/zram<id>/idle
0103 Date: November 2018
0104 Contact: Minchan Kim <minchan@kernel.org>
0105 Description:
0106 idle file is write-only and mark zram slot as idle.
0107 If system has mounted debugfs, user can see which slots
0108 are idle via /sys/kernel/debug/zram/zram<id>/block_state
0109
0110 What: /sys/block/zram<id>/writeback
0111 Date: November 2018
0112 Contact: Minchan Kim <minchan@kernel.org>
0113 Description:
0114 The writeback file is write-only and trigger idle and/or
0115 huge page writeback to backing device.
0116
0117 What: /sys/block/zram<id>/bd_stat
0118 Date: November 2018
0119 Contact: Minchan Kim <minchan@kernel.org>
0120 Description:
0121 The bd_stat file is read-only and represents backing device's
0122 statistics (bd_count, bd_reads, bd_writes) in a format
0123 similar to block layer statistics file format.
0124
0125 What: /sys/block/zram<id>/writeback_limit_enable
0126 Date: November 2018
0127 Contact: Minchan Kim <minchan@kernel.org>
0128 Description:
0129 The writeback_limit_enable file is read-write and specifies
0130 eanbe of writeback_limit feature. "1" means eable the feature.
0131 No limit "0" is the initial state.
0132
0133 What: /sys/block/zram<id>/writeback_limit
0134 Date: November 2018
0135 Contact: Minchan Kim <minchan@kernel.org>
0136 Description:
0137 The writeback_limit file is read-write and specifies the maximum
0138 amount of writeback ZRAM can do. The limit could be changed
0139 in run time.
