Lines Matching +full:512 +full:- +full:bytes

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.
62 		Number of bytes of integrity tag space available per
63 		512 bytes of data.
71 		integrity metadata. Set if the device is T10 PI-capable.
77 		Describes the number of data bytes which are protected
95 		with 4KB physical sectors exposing 512-byte logical
97 		indicates how many bytes the beginning of the device is
106 		with 4KB physical sectors exposing 512-byte logical
108 		indicates how many bytes the beginning of the partition
116 		address.  It is typically 512 bytes.
125 		drives with 4KB sectors that expose a 512-byte logical
166 		merge checks are disabled, but the simple one-shot merges
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
201 		unit in bytes if reported by the device. Otherwise the
211 		internal limits on the number of bytes that can be
216 		to the maximum number of bytes that can be discarded in
238 		bytes can be written in a single write same command. If
251 		bytes can be written in a single write zeroes command. If
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
304 		indicates the size in 512B sectors of the RAID volume
306 		host-aware or host-managed, chunk_sectors indicates the
307 		size in 512B sectors of the zones of the device, with