aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/ABI/testing/sysfs-block-zram
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/ABI/testing/sysfs-block-zram')
-rw-r--r--Documentation/ABI/testing/sysfs-block-zram32
1 files changed, 27 insertions, 5 deletions
diff --git a/Documentation/ABI/testing/sysfs-block-zram b/Documentation/ABI/testing/sysfs-block-zram
index 70ec992514d0..a6148eaf91e5 100644
--- a/Documentation/ABI/testing/sysfs-block-zram
+++ b/Documentation/ABI/testing/sysfs-block-zram
@@ -77,11 +77,14 @@ What: /sys/block/zram<id>/notify_free
77Date: August 2010 77Date: August 2010
78Contact: Nitin Gupta <ngupta@vflare.org> 78Contact: Nitin Gupta <ngupta@vflare.org>
79Description: 79Description:
80 The notify_free file is read-only and specifies the number of 80 The notify_free file is read-only. Depending on device usage
81 swap slot free notifications received by this device. These 81 scenario it may account a) the number of pages freed because
82 notifications are sent to a swap block device when a swap slot 82 of swap slot free notifications or b) the number of pages freed
83 is freed. This statistic is applicable only when this disk is 83 because of REQ_DISCARD requests sent by bio. The former ones
84 being used as a swap disk. 84 are sent to a swap block device when a swap slot is freed, which
85 implies that this disk is being used as a swap disk. The latter
86 ones are sent by filesystem mounted with discard option,
87 whenever some data blocks are getting discarded.
85 88
86What: /sys/block/zram<id>/zero_pages 89What: /sys/block/zram<id>/zero_pages
87Date: August 2010 90Date: August 2010
@@ -119,3 +122,22 @@ Description:
119 efficiency can be calculated using compr_data_size and this 122 efficiency can be calculated using compr_data_size and this
120 statistic. 123 statistic.
121 Unit: bytes 124 Unit: bytes
125
126What: /sys/block/zram<id>/mem_used_max
127Date: August 2014
128Contact: Minchan Kim <minchan@kernel.org>
129Description:
130 The mem_used_max file is read/write and specifies the amount
131 of maximum memory zram have consumed to store compressed data.
132 For resetting the value, you should write "0". Otherwise,
133 you could see -EINVAL.
134 Unit: bytes
135
136What: /sys/block/zram<id>/mem_limit
137Date: August 2014
138Contact: Minchan Kim <minchan@kernel.org>
139Description:
140 The mem_limit file is read/write and specifies the maximum
141 amount of memory ZRAM can use to store the compressed data. The
142 limit could be changed in run time and "0" means disable the
143 limit. No limit is the initial state. Unit: bytes