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
31 operation must not exceed this number of bytes.
35 power-of-two and atomic_write_unit_max_bytes may also be
37 This parameter - along with atomic_write_unit_min_bytes
38 and atomic_write_unit_max_bytes - will not be larger than
50 atomic_write_unit_min. This value must be a power-of-two.
60 be a power-of-two. This value will not be larger than
70 parameter specifies the size in bytes of the atomic boundary if
72 power-of-two and at least the size as in
111 integrity metadata. Set if the device is T10 PI-capable.
119 E.g. T10-DIF-TYPE1-CRC.
126 Describes the number of data bytes which are protected
144 Number of bytes of integrity tag space available per
145 512 bytes of data.
163 scanning is enabled, or "0" if not. The value type is a 32-bit
173 with 4KB physical sectors exposing 512-byte logical
175 indicates how many bytes the beginning of the partition
186 parameter indicates how many bytes the beginning of the
202 Contact: linux-block@vger.kernel.org
213 of the disk. For a RAID device (dm-raid), chunk_sectors
214 indicates the size in 512B sectors of the RAID volume stripe
215 segment. For a zoned block device, either host-aware or
216 host-managed, chunk_sectors indicates the size in 512B sectors
223 Contact: linux-block@vger.kernel.org
229 encryption, refer to Documentation/block/inline-encryption.rst.
234 Contact: linux-block@vger.kernel.org
242 Contact: linux-block@vger.kernel.org
248 bytes, for that crypto mode.
252 * AES-256-XTS
253 * AES-128-CBC-ESSIV
256 For example, if a device supports AES-256-XTS inline encryption
257 with data unit sizes of 512 and 4096 bytes, the file
258 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
264 Contact: linux-block@vger.kernel.org
272 Contact: linux-block@vger.kernel.org
275 Access (DAX), used by CPU-addressable storage to bypass the
286 of the internal allocation unit in bytes if reported by the
306 Contact: linux-block@vger.kernel.org
309 internal limits on the number of bytes that can be trimmed or
312 bytes that can be discarded in a single operation. Discard
328 Contact: linux-block@vger.kernel.org
337 Contact: linux-block@vger.kernel.org
347 Contact: linux-block@vger.kernel.org
349 [RO] This is the hardware sector size of the device, in bytes.
354 Contact: linux-block@vger.kernel.org
356 [RO] The presence of this sub-directory of the
359 in parallel. For instance, single LUN multi-actuator hard-disks
368 the range. For example, a dual-actuator hard-disk will have the
373 |-- 0
374 | |-- nr_sectors
375 | `-- sector
376 `-- 1
377 |-- nr_sectors
378 `-- sector
380 The sector and nr_sectors attributes use 512B sector unit,
390 Contact: linux-block@vger.kernel.org
394 for this device. Writing any non-zero value will enable this
400 Contact: linux-block@vger.kernel.org
403 performed. It is now fixed to -1, which is classic polling.
422 Contact: linux-block@vger.kernel.org
433 It is typically 512 bytes.
441 "host-managed" or "host-aware"), the sum of zones belonging to
452 Contact: linux-block@vger.kernel.org
460 Contact: linux-block@vger.kernel.org
468 Contact: linux-block@vger.kernel.org
480 "host-managed" or "host-aware"), the sum of zones belonging to
487 Contact: linux-block@vger.kernel.org
497 Contact: linux-block@vger.kernel.org
499 [RO] Maximum size in bytes of a single element in a DMA
505 Contact: linux-block@vger.kernel.org
526 Contact: linux-block@vger.kernel.org
533 simple one-shot merges with the previous I/O request are
535 default value is 0 - which enables all types of merge tries.
540 Contact: linux-block@vger.kernel.org
550 each such per-block-cgroup request pool. IOW, if there are N
560 block device ("host-aware" or "host-managed" zone model). For
584 sectors that expose a 512-byte logical block size to the
592 Contact: linux-block@vger.kernel.org
594 [RW] Maximum number of kilobytes to read-ahead for filesystems
603 Contact: linux-block@vger.kernel.org
606 type or non-rotational type.
611 Contact: linux-block@vger.kernel.org
626 Contact: linux-block@vger.kernel.org
639 Contact: linux-block@vger.kernel.org
648 times where the same data must be seen every time -- for
655 Contact: linux-block@vger.kernel.org
662 bytes.
667 Contact: linux-block@vger.kernel.org
674 value of '-1' to this file resets the value to the default
680 Contact: linux-block@vger.kernel.org
700 write_same_max_bytes indicates how many bytes can be written in
713 write_zeroes_max_bytes indicates how many bytes can be written
720 Contact: linux-block@vger.kernel.org
722 [RO] This is the maximum number of bytes that can be written to
730 Contact: linux-block@vger.kernel.org
732 [RO] This indicates the alignment constraint, in bytes, for
734 (devices with a zoned attributed that reports "host-managed" or
735 "host-aware"). This value is always 0 for regular block devices.
745 devices and "host-aware" or "host-managed" for zoned block
746 devices. The characteristics of host-aware and host-managed
749 These standards also define the "drive-managed" zone model.
750 However, since drive-managed zoned block devices do not support
757 Contact: linux-block@vger.kernel.org
791 For more details refer Documentation/admin-guide/iostats.rst