Lines Matching +full:current +full:- +full:regulated
7 with 4KB physical sectors exposing 512-byte logical
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
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.
163 scanning is enabled, or "0" if not. The value type is a 32-bit
173 with 4KB physical sectors exposing 512-byte logical
202 Contact: linux-[email protected]
213 of the disk. For a RAID device (dm-raid), chunk_sectors
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-[email protected]
229 encryption, refer to Documentation/block/inline-encryption.rst.
234 Contact: linux-[email protected]
242 Contact: linux-[email protected]
252 * AES-256-XTS
253 * AES-128-CBC-ESSIV
256 For example, if a device supports AES-256-XTS inline encryption
258 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
264 Contact: linux-[email protected]
272 Contact: linux-[email protected]
275 Access (DAX), used by CPU-addressable storage to bypass the
306 Contact: linux-[email protected]
328 Contact: linux-[email protected]
337 Contact: linux-[email protected]
347 Contact: linux-[email protected]
354 Contact: linux-[email protected]
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
390 Contact: linux-[email protected]
394 for this device. Writing any non-zero value will enable this
400 Contact: linux-[email protected]
403 performed. It is now fixed to -1, which is classic polling.
422 Contact: linux-[email protected]
429 Contact: linux-[email protected]
448 "host-managed" or "host-aware"), the sum of zones belonging to
459 Contact: linux-[email protected]
467 Contact: linux-[email protected]
475 Contact: linux-[email protected]
487 "host-managed" or "host-aware"), the sum of zones belonging to
494 Contact: linux-[email protected]
504 Contact: linux-[email protected]
512 Contact: linux-[email protected]
533 Contact: linux-[email protected]
540 simple one-shot merges with the previous I/O request are
542 default value is 0 - which enables all types of merge tries.
547 Contact: linux-[email protected]
557 each such per-block-cgroup request pool. IOW, if there are N
559 pools, each independently regulated by nr_requests.
567 block device ("host-aware" or "host-managed" zone model). For
591 sectors that expose a 512-byte logical block size to the
599 Contact: linux-[email protected]
601 [RW] Maximum number of kilobytes to read-ahead for filesystems
610 Contact: linux-[email protected]
613 type or non-rotational type.
618 Contact: linux-[email protected]
633 Contact: linux-[email protected]
635 [RW] When read, this file will display the current and available
646 Contact: linux-[email protected]
655 times where the same data must be seen every time -- for
662 Contact: linux-[email protected]
668 of the current segment is not aligned to virt_boundary_mask + 1
674 Contact: linux-[email protected]
681 value of '-1' to this file resets the value to the default
687 Contact: linux-[email protected]
727 Contact: linux-[email protected]
737 Contact: linux-[email protected]
741 (devices with a zoned attributed that reports "host-managed" or
742 "host-aware"). This value is always 0 for regular block devices.
752 devices and "host-aware" or "host-managed" for zoned block
753 devices. The characteristics of host-aware and host-managed
756 These standards also define the "drive-managed" zone model.
757 However, since drive-managed zoned block devices do not support
764 Contact: linux-[email protected]
798 For more details refer Documentation/admin-guide/iostats.rst