Lines Matching +full:many +full:- +full:to +full:- +full:one
28 For more details refer Documentation/admin-guide/iostats.rst
37 same as the above-written /sys/block/<disk>/stat
46 E.g. T10-DIF-TYPE1-CRC.
71 integrity metadata. Set if the device is T10 PI-capable.
78 by one integrity tuple. Typically the device's logical
95 with 4KB physical sectors exposing 512-byte logical
96 blocks to the operating system). This parameter
97 indicates how many bytes the beginning of the device is
106 with 4KB physical sectors exposing 512-byte logical
107 blocks to the operating system). This parameter
108 indicates how many bytes the beginning of the partition
124 block size but may be bigger. One example is SATA
125 drives with 4KB sectors that expose a 512-byte logical
126 block size to the operating system. For stacked block
161 Standard I/O elevator operations include attempts to
164 being spent in the kernel. This allows one to turn off
165 this behavior on one of two ways: When set to 1, complex
166 merge checks are disabled, but the simple one-shot merges
167 with the previous I/O request are enabled. When set to 2,
168 all merge tries are disabled. The default value is 0 -
178 parameter indicates how many bytes the beginning of the
189 parameter indicates how many bytes the beginning of the
202 discard_granularity will be set to match the device's
216 to the maximum number of bytes that can be discarded in
217 a single operation. Discard requests issued to the
234 single data block can be written to a range of several
235 contiguous blocks on storage. This can be used to wipe
236 areas on disk or to initialize drives in a RAID
237 configuration. write_same_max_bytes indicates how many
247 single request can be issued to zero out the range of
249 in the request. This can be used to optimize writing zeroes
250 to the devices. write_zeroes_max_bytes indicates how many
262 regular block devices and "host-aware" or "host-managed"
264 host-aware and host-managed zoned block devices are
267 also define the "drive-managed" zone model. However,
268 since drive-managed zoned block devices do not support
277 device ("host-aware" or "host-managed" zone model). For regular
285 "host-managed" or "host-aware"), the sum of zones belonging to
294 "host-managed" or "host-aware"), the sum of zones belonging to
303 of the disk. For a RAID device (dm-raid), chunk_sectors
306 host-aware or host-managed, chunk_sectors indicates the
317 handler is invoked. That timeout handler can decide to retry
318 the request, to fail it or to start a device recovery strategy.