write in 30M

hc

2024-02-20 ea08eeccae9297f7aabd2ef7f0c2517ac4549acc

 kernel/Documentation/ABI/testing/sysfs-block
..
..
@@ -4,18 +4,28 @@
4
4
 Description:
5
5
 		The /sys/block/<disk>/stat files displays the I/O
6
6
 		statistics of disk <disk>. They contain 11 fields:
7
-		 1 - reads completed successfully
8
-		 2 - reads merged
9
-		 3 - sectors read
10
-		 4 - time spent reading (ms)
11
-		 5 - writes completed
12
-		 6 - writes merged
13
-		 7 - sectors written
14
-		 8 - time spent writing (ms)
15
-		 9 - I/Os currently in progress
16
-		10 - time spent doing I/Os (ms)
17
-		11 - weighted time spent doing I/Os (ms)
18
-		For more details refer Documentation/iostats.txt
7
+
8
+		==  ==============================================
9
+		 1  reads completed successfully
10
+		 2  reads merged
11
+		 3  sectors read
12
+		 4  time spent reading (ms)
13
+		 5  writes completed
14
+		 6  writes merged
15
+		 7  sectors written
16
+		 8  time spent writing (ms)
17
+		 9  I/Os currently in progress
18
+		10  time spent doing I/Os (ms)
19
+		11  weighted time spent doing I/Os (ms)
20
+		12  discards completed
21
+		13  discards merged
22
+		14  sectors discarded
23
+		15  time spent discarding (ms)
24
+		16  flush requests completed
25
+		17  time spent flushing (ms)
26
+		==  ==============================================
27
+
28
+		For more details refer Documentation/admin-guide/iostats.rst
19
29
 
20
30
 
21
31
 What:		/sys/block/<disk>/<part>/stat
..
..
@@ -244,7 +254,7 @@
244
254
 
245
255
 What:		/sys/block/<disk>/queue/zoned
246
256
 Date:		September 2016
247
-Contact:	Damien Le Moal <damien.lemoal@hgst.com>
257
+Contact:	Damien Le Moal <damien.lemoal@wdc.com>
248
258
 Description:
249
259
 		zoned indicates if the device is a zoned block device
250
260
 		and the zone model of the device if it is indeed zoned.
..
..
@@ -259,6 +269,32 @@
259
269
 		zone commands, they will be treated as regular block
260
270
 		devices and zoned will report "none".
261
271
 
272
+What:		/sys/block/<disk>/queue/nr_zones
273
+Date:		November 2018
274
+Contact:	Damien Le Moal <damien.lemoal@wdc.com>
275
+Description:
276
+		nr_zones indicates the total number of zones of a zoned block
277
+		device ("host-aware" or "host-managed" zone model). For regular
278
+		block devices, the value is always 0.
279
+
280
+What:		/sys/block/<disk>/queue/max_active_zones
281
+Date:		July 2020
282
+Contact:	Niklas Cassel <niklas.cassel@wdc.com>
283
+Description:
284
+		For zoned block devices (zoned attribute indicating
285
+		"host-managed" or "host-aware"), the sum of zones belonging to
286
+		any of the zone states: EXPLICIT OPEN, IMPLICIT OPEN or CLOSED,
287
+		is limited by this value. If this value is 0, there is no limit.
288
+
289
+What:		/sys/block/<disk>/queue/max_open_zones
290
+Date:		July 2020
291
+Contact:	Niklas Cassel <niklas.cassel@wdc.com>
292
+Description:
293
+		For zoned block devices (zoned attribute indicating
294
+		"host-managed" or "host-aware"), the sum of zones belonging to
295
+		any of the zone states: EXPLICIT OPEN or IMPLICIT OPEN,
296
+		is limited by this value. If this value is 0, there is no limit.
297
+
262
298
 What:		/sys/block/<disk>/queue/chunk_sectors
263
299
 Date:		September 2016
264
300
 Contact:	Hannes Reinecke <hare@suse.com>
..
..
@@ -268,6 +304,15 @@
268
304
 		indicates the size in 512B sectors of the RAID volume
269
305
 		stripe segment. For a zoned block device, either
270
306
 		host-aware or host-managed, chunk_sectors indicates the
271
-		size of 512B sectors of the zones of the device, with
307
+		size in 512B sectors of the zones of the device, with
272
308
 		the eventual exception of the last zone of the device
273
309
 		which may be smaller.
310
+
311
+What:		/sys/block/<disk>/queue/io_timeout
312
+Date:		November 2018
313
+Contact:	Weiping Zhang <zhangweiping@didiglobal.com>
314
+Description:
315
+		io_timeout is the request timeout in milliseconds. If a request
316
+		does not complete in this time then the block driver timeout
317
+		handler is invoked. That timeout handler can decide to retry
318
+		the request, to fail it or to start a device recovery strategy.