Lines Matching +full:512 +full:- +full:bytes
7 with 4KB physical sectors exposing 512-byte logical
9 indicates how many bytes the beginning of the device is
20 parameter indicates how many bytes the beginning of the
58 integrity metadata. Set if the device is T10 PI-capable.
66 E.g. T10-DIF-TYPE1-CRC.
73 Describes the number of data bytes which are protected
91 Number of bytes of integrity tag space available per
92 512 bytes of data.
110 with 4KB physical sectors exposing 512-byte logical
112 indicates how many bytes the beginning of the partition
123 parameter indicates how many bytes the beginning of the
139 Contact: linux-block@vger.kernel.org
150 of the disk. For a RAID device (dm-raid), chunk_sectors
151 indicates the size in 512B sectors of the RAID volume stripe
152 segment. For a zoned block device, either host-aware or
153 host-managed, chunk_sectors indicates the size in 512B sectors
160 Contact: linux-block@vger.kernel.org
166 encryption, refer to Documentation/block/inline-encryption.rst.
171 Contact: linux-block@vger.kernel.org
179 Contact: linux-block@vger.kernel.org
185 bytes, for that crypto mode.
189 * AES-256-XTS
190 * AES-128-CBC-ESSIV
193 For example, if a device supports AES-256-XTS inline encryption
194 with data unit sizes of 512 and 4096 bytes, the file
195 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
201 Contact: linux-block@vger.kernel.org
209 Contact: linux-block@vger.kernel.org
212 Access (DAX), used by CPU-addressable storage to bypass the
223 of the internal allocation unit in bytes if reported by the
243 Contact: linux-block@vger.kernel.org
246 internal limits on the number of bytes that can be trimmed or
249 bytes that can be discarded in a single operation. Discard
265 Contact: linux-block@vger.kernel.org
274 Contact: linux-block@vger.kernel.org
284 Contact: linux-block@vger.kernel.org
286 [RO] This is the hardware sector size of the device, in bytes.
291 Contact: linux-block@vger.kernel.org
293 [RO] The presence of this sub-directory of the
296 in parallel. For instance, single LUN multi-actuator hard-disks
305 the range. For example, a dual-actuator hard-disk will have the
310 |-- 0
311 | |-- nr_sectors
312 | `-- sector
313 `-- 1
314 |-- nr_sectors
315 `-- sector
317 The sector and nr_sectors attributes use 512B sector unit,
327 Contact: linux-block@vger.kernel.org
331 for this device. Writing any non-zero value will enable this
337 Contact: linux-block@vger.kernel.org
340 performed. It is now fixed to -1, which is classic polling.
359 Contact: linux-block@vger.kernel.org
370 It is typically 512 bytes.
378 "host-managed" or "host-aware"), the sum of zones belonging to
389 Contact: linux-block@vger.kernel.org
397 Contact: linux-block@vger.kernel.org
405 Contact: linux-block@vger.kernel.org
417 "host-managed" or "host-aware"), the sum of zones belonging to
424 Contact: linux-block@vger.kernel.org
434 Contact: linux-block@vger.kernel.org
436 [RO] Maximum size in bytes of a single element in a DMA
442 Contact: linux-block@vger.kernel.org
463 Contact: linux-block@vger.kernel.org
470 simple one-shot merges with the previous I/O request are
472 default value is 0 - which enables all types of merge tries.
477 Contact: linux-block@vger.kernel.org
487 each such per-block-cgroup request pool. IOW, if there are N
497 block device ("host-aware" or "host-managed" zone model). For
521 sectors that expose a 512-byte logical block size to the
529 Contact: linux-block@vger.kernel.org
531 [RW] Maximum number of kilobytes to read-ahead for filesystems
537 Contact: linux-block@vger.kernel.org
540 type or non-rotational type.
545 Contact: linux-block@vger.kernel.org
560 Contact: linux-block@vger.kernel.org
573 Contact: linux-block@vger.kernel.org
582 times where the same data must be seen every time -- for
590 Contact: linux-block@vger.kernel.org
592 [RW] This is the time window that blk-throttle samples data, in
593 millisecond. blk-throttle makes decision based on the
601 Contact: linux-block@vger.kernel.org
608 bytes.
613 Contact: linux-block@vger.kernel.org
620 value of '-1' to this file resets the value to the default
626 Contact: linux-block@vger.kernel.org
646 write_same_max_bytes indicates how many bytes can be written in
659 write_zeroes_max_bytes indicates how many bytes can be written
666 Contact: linux-block@vger.kernel.org
668 [RO] This is the maximum number of bytes that can be written to
676 Contact: linux-block@vger.kernel.org
678 [RO] This indicates the alignment constraint, in bytes, for
680 (devices with a zoned attributed that reports "host-managed" or
681 "host-aware"). This value is always 0 for regular block devices.
691 devices and "host-aware" or "host-managed" for zoned block
692 devices. The characteristics of host-aware and host-managed
695 These standards also define the "drive-managed" zone model.
696 However, since drive-managed zoned block devices do not support
703 Contact: linux-block@vger.kernel.org
737 For more details refer Documentation/admin-guide/iostats.rst