Lines Matching +full:os +full:- +full:data +full:- +full:offset
7 with 4KB physical sectors exposing 512-byte logical
10 offset from the disk's natural alignment.
21 device is offset from the internal allocation unit's
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
74 Any attempt to merge atomic write I/Os must not result in a
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
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
176 is offset from the disk's natural alignment.
187 partition is offset from the internal allocation unit's
202 Contact: linux-block@vger.kernel.org
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-block@vger.kernel.org
229 encryption, refer to Documentation/block/inline-encryption.rst.
234 Contact: linux-block@vger.kernel.org
236 [RO] This file shows the maximum length, in bits, of data unit
242 Contact: linux-block@vger.kernel.org
247 number that is a bitmask of the supported data unit sizes, in
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
306 Contact: linux-block@vger.kernel.org
328 Contact: linux-block@vger.kernel.org
337 Contact: linux-block@vger.kernel.org
347 Contact: linux-block@vger.kernel.org
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
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
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
463 single data transfer.
468 Contact: linux-block@vger.kernel.org
471 with integrity data that will be submitted by the block layer
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
505 Contact: linux-block@vger.kernel.org
526 Contact: linux-block@vger.kernel.org
529 contiguous I/Os. For known random I/O loads these attempts will
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
650 the data. If no such restriction exists, this file will contain
655 Contact: linux-block@vger.kernel.org
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
697 single data block can be written to a range of several
720 Contact: linux-block@vger.kernel.org
730 Contact: linux-block@vger.kernel.org
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
780 9 I/Os currently in progress
781 10 time spent doing I/Os (ms)
782 11 weighted time spent doing I/Os (ms)
791 For more details refer Documentation/admin-guide/iostats.rst