Lines Matching +full:current +full:- +full:regulated
7 with 4KB physical sectors exposing 512-byte logical
58 integrity metadata. Set if the device is T10 PI-capable.
66 E.g. T10-DIF-TYPE1-CRC.
110 scanning is enabled, or "0" if not. The value type is a 32-bit
120 with 4KB physical sectors exposing 512-byte logical
149 Contact: linux-block@vger.kernel.org
160 of the disk. For a RAID device (dm-raid), chunk_sectors
162 segment. For a zoned block device, either host-aware or
163 host-managed, chunk_sectors indicates the size in 512B sectors
170 Contact: linux-block@vger.kernel.org
176 encryption, refer to Documentation/block/inline-encryption.rst.
181 Contact: linux-block@vger.kernel.org
189 Contact: linux-block@vger.kernel.org
199 * AES-256-XTS
200 * AES-128-CBC-ESSIV
203 For example, if a device supports AES-256-XTS inline encryption
205 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
211 Contact: linux-block@vger.kernel.org
219 Contact: linux-block@vger.kernel.org
222 Access (DAX), used by CPU-addressable storage to bypass the
253 Contact: linux-block@vger.kernel.org
275 Contact: linux-block@vger.kernel.org
284 Contact: linux-block@vger.kernel.org
294 Contact: linux-block@vger.kernel.org
301 Contact: linux-block@vger.kernel.org
303 [RO] The presence of this sub-directory of the
306 in parallel. For instance, single LUN multi-actuator hard-disks
315 the range. For example, a dual-actuator hard-disk will have the
320 |-- 0
321 | |-- nr_sectors
322 | `-- sector
323 `-- 1
324 |-- nr_sectors
325 `-- sector
337 Contact: linux-block@vger.kernel.org
341 for this device. Writing any non-zero value will enable this
347 Contact: linux-block@vger.kernel.org
350 performed. It is now fixed to -1, which is classic polling.
369 Contact: linux-block@vger.kernel.org
388 "host-managed" or "host-aware"), the sum of zones belonging to
399 Contact: linux-block@vger.kernel.org
407 Contact: linux-block@vger.kernel.org
415 Contact: linux-block@vger.kernel.org
427 "host-managed" or "host-aware"), the sum of zones belonging to
434 Contact: linux-block@vger.kernel.org
444 Contact: linux-block@vger.kernel.org
452 Contact: linux-block@vger.kernel.org
473 Contact: linux-block@vger.kernel.org
480 simple one-shot merges with the previous I/O request are
482 default value is 0 - which enables all types of merge tries.
487 Contact: linux-block@vger.kernel.org
497 each such per-block-cgroup request pool. IOW, if there are N
499 pools, each independently regulated by nr_requests.
507 block device ("host-aware" or "host-managed" zone model). For
531 sectors that expose a 512-byte logical block size to the
539 Contact: linux-block@vger.kernel.org
541 [RW] Maximum number of kilobytes to read-ahead for filesystems
547 Contact: linux-block@vger.kernel.org
550 type or non-rotational type.
555 Contact: linux-block@vger.kernel.org
570 Contact: linux-block@vger.kernel.org
572 [RW] When read, this file will display the current and available
583 Contact: linux-block@vger.kernel.org
592 times where the same data must be seen every time -- for
600 Contact: linux-block@vger.kernel.org
602 [RW] This is the time window that blk-throttle samples data, in
603 millisecond. blk-throttle makes decision based on the
611 Contact: linux-block@vger.kernel.org
617 of the current segment is not aligned to virt_boundary_mask + 1
623 Contact: linux-block@vger.kernel.org
630 value of '-1' to this file resets the value to the default
636 Contact: linux-block@vger.kernel.org
676 Contact: linux-block@vger.kernel.org
686 Contact: linux-block@vger.kernel.org
690 (devices with a zoned attributed that reports "host-managed" or
691 "host-aware"). This value is always 0 for regular block devices.
701 devices and "host-aware" or "host-managed" for zoned block
702 devices. The characteristics of host-aware and host-managed
705 These standards also define the "drive-managed" zone model.
706 However, since drive-managed zoned block devices do not support
713 Contact: linux-block@vger.kernel.org
747 For more details refer Documentation/admin-guide/iostats.rst