@@ -21,6 +21,59 @@ Description:
2121 device is offset from the internal allocation unit's
2222 natural alignment.
2323
24+ What: /sys/block/<disk>/atomic_write_max_bytes
25+ Date: February 2024
26+ Contact: Himanshu Madhani <
[email protected] >
27+ Description:
28+ [RO] This parameter specifies the maximum atomic write
29+ size reported by the device. This parameter is relevant
30+ for merging of writes, where a merged atomic write
31+ operation must not exceed this number of bytes.
32+ This parameter may be greater than the value in
33+ atomic_write_unit_max_bytes as
34+ atomic_write_unit_max_bytes will be rounded down to a
35+ power-of-two and atomic_write_unit_max_bytes may also be
36+ limited by some other queue limits, such as max_segments.
37+ This parameter - along with atomic_write_unit_min_bytes
38+ and atomic_write_unit_max_bytes - will not be larger than
39+ max_hw_sectors_kb, but may be larger than max_sectors_kb.
40+
41+
42+ What: /sys/block/<disk>/atomic_write_unit_min_bytes
43+ Date: February 2024
44+ Contact: Himanshu Madhani <
[email protected] >
45+ Description:
46+ [RO] This parameter specifies the smallest block which can
47+ be written atomically with an atomic write operation. All
48+ atomic write operations must begin at a
49+ atomic_write_unit_min boundary and must be multiples of
50+ atomic_write_unit_min. This value must be a power-of-two.
51+
52+
53+ What: /sys/block/<disk>/atomic_write_unit_max_bytes
54+ Date: February 2024
55+ Contact: Himanshu Madhani <
[email protected] >
56+ Description:
57+ [RO] This parameter defines the largest block which can be
58+ written atomically with an atomic write operation. This
59+ value must be a multiple of atomic_write_unit_min and must
60+ be a power-of-two. This value will not be larger than
61+ atomic_write_max_bytes.
62+
63+
64+ What: /sys/block/<disk>/atomic_write_boundary_bytes
65+ Date: February 2024
66+ Contact: Himanshu Madhani <
[email protected] >
67+ Description:
68+ [RO] A device may need to internally split an atomic write I/O
69+ which straddles a given logical block address boundary. This
70+ parameter specifies the size in bytes of the atomic boundary if
71+ one is reported by the device. This value must be a
72+ power-of-two and at least the size as in
73+ atomic_write_unit_max_bytes.
74+ Any attempt to merge atomic write I/Os must not result in a
75+ merged I/O which crosses this boundary (if any).
76+
2477
2578What: /sys/block/<disk>/diskseq
2679Date: February 2021
@@ -101,6 +154,16 @@ Description:
101154 devices that support receiving integrity metadata.
102155
103156
157+ What: /sys/block/<disk>/partscan
158+ Date: May 2024
159+ Contact: Christoph Hellwig <
[email protected] >
160+ Description:
161+ The /sys/block/<disk>/partscan files reports if partition
162+ scanning is enabled for the disk. It returns "1" if partition
163+ scanning is enabled, or "0" if not. The value type is a 32-bit
164+ unsigned integer, but only "0" and "1" are valid values.
165+
166+
104167What: /sys/block/<disk>/<partition>/alignment_offset
105168Date: April 2009
106169Contact: Martin K. Petersen <
[email protected] >
@@ -584,18 +647,6 @@ Description:
584647 the data. If no such restriction exists, this file will contain
585648 '0'. This file is writable for testing purposes.
586649
587-
588- What: /sys/block/<disk>/queue/throttle_sample_time
589- Date: March 2017
590- 591- Description:
592- [RW] This is the time window that blk-throttle samples data, in
593- millisecond. blk-throttle makes decision based on the
594- samplings. Lower time means cgroups have more smooth throughput,
595- but higher CPU overhead. This exists only when
596- CONFIG_BLK_DEV_THROTTLING_LOW is enabled.
597-
598-
599650What: /sys/block/<disk>/queue/virt_boundary_mask
600651Date: April 2021
601652
0 commit comments