blob: 8aa0468416255bb85c2a97b1900f62d15ed2a5f3 [file] [log] [blame]
Nitin Guptae98419c2010-08-09 22:56:56 +05301What: /sys/block/zram<id>/disksize
2Date: August 2010
3Contact: Nitin Gupta <ngupta@vflare.org>
4Description:
5 The disksize file is read-write and specifies the disk size
6 which represents the limit on the *uncompressed* worth of data
7 that can be stored in this disk.
Bernhard M. Wiedemann51d8a7b2013-08-26 14:55:44 -07008 Unit: bytes
Nitin Guptae98419c2010-08-09 22:56:56 +05309
10What: /sys/block/zram<id>/initstate
11Date: August 2010
12Contact: Nitin Gupta <ngupta@vflare.org>
13Description:
Bernhard M. Wiedemann51d8a7b2013-08-26 14:55:44 -070014 The initstate file is read-only and shows the initialization
Nitin Guptae98419c2010-08-09 22:56:56 +053015 state of the device.
16
17What: /sys/block/zram<id>/reset
18Date: August 2010
19Contact: Nitin Gupta <ngupta@vflare.org>
20Description:
Bernhard M. Wiedemann51d8a7b2013-08-26 14:55:44 -070021 The reset file is write-only and allows resetting the
22 device. The reset operation frees all the memory associated
Nitin Guptae98419c2010-08-09 22:56:56 +053023 with this device.
24
25What: /sys/block/zram<id>/num_reads
26Date: August 2010
27Contact: Nitin Gupta <ngupta@vflare.org>
28Description:
29 The num_reads file is read-only and specifies the number of
30 reads (failed or successful) done on this device.
31
32What: /sys/block/zram<id>/num_writes
33Date: August 2010
34Contact: Nitin Gupta <ngupta@vflare.org>
35Description:
36 The num_writes file is read-only and specifies the number of
37 writes (failed or successful) done on this device.
38
39What: /sys/block/zram<id>/invalid_io
40Date: August 2010
41Contact: Nitin Gupta <ngupta@vflare.org>
42Description:
43 The invalid_io file is read-only and specifies the number of
44 non-page-size-aligned I/O requests issued to this device.
45
Sergey Senozhatsky8dd1d322014-04-07 15:38:08 -070046What: /sys/block/zram<id>/failed_reads
47Date: February 2014
48Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
49Description:
50 The failed_reads file is read-only and specifies the number of
51 failed reads happened on this device.
52
53
54What: /sys/block/zram<id>/failed_writes
55Date: February 2014
56Contact: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
57Description:
58 The failed_writes file is read-only and specifies the number of
59 failed writes happened on this device.
60
Nitin Guptae98419c2010-08-09 22:56:56 +053061What: /sys/block/zram<id>/notify_free
62Date: August 2010
63Contact: Nitin Gupta <ngupta@vflare.org>
64Description:
65 The notify_free file is read-only and specifies the number of
66 swap slot free notifications received by this device. These
Bernhard M. Wiedemann51d8a7b2013-08-26 14:55:44 -070067 notifications are sent to a swap block device when a swap slot
Nitin Guptae98419c2010-08-09 22:56:56 +053068 is freed. This statistic is applicable only when this disk is
69 being used as a swap disk.
70
Nitin Guptae98419c2010-08-09 22:56:56 +053071What: /sys/block/zram<id>/zero_pages
72Date: August 2010
73Contact: Nitin Gupta <ngupta@vflare.org>
74Description:
75 The zero_pages file is read-only and specifies number of zero
76 filled pages written to this disk. No memory is allocated for
77 such pages.
78
79What: /sys/block/zram<id>/orig_data_size
80Date: August 2010
81Contact: Nitin Gupta <ngupta@vflare.org>
82Description:
83 The orig_data_size file is read-only and specifies uncompressed
84 size of data stored in this disk. This excludes zero-filled
85 pages (zero_pages) since no memory is allocated for them.
86 Unit: bytes
87
88What: /sys/block/zram<id>/compr_data_size
89Date: August 2010
90Contact: Nitin Gupta <ngupta@vflare.org>
91Description:
92 The compr_data_size file is read-only and specifies compressed
93 size of data stored in this disk. So, compression ratio can be
94 calculated using orig_data_size and this statistic.
95 Unit: bytes
96
97What: /sys/block/zram<id>/mem_used_total
98Date: August 2010
99Contact: Nitin Gupta <ngupta@vflare.org>
100Description:
101 The mem_used_total file is read-only and specifies the amount
102 of memory, including allocator fragmentation and metadata
103 overhead, allocated for this disk. So, allocator space
104 efficiency can be calculated using compr_data_size and this
105 statistic.
Jesper Juhlf9028312012-07-20 22:35:17 +0200106 Unit: bytes