Lines Matching +full:block +full:- +full:number
1 What: /sys/block/<disk>/alignment_offset
5 Storage devices may report a physical block size that is
6 bigger than the logical block size (for instance a drive
7 with 4KB physical sectors exposing 512-byte logical
13 What: /sys/block/<disk>/discard_alignment
19 the exported logical block size. The discard_alignment
24 What: /sys/block/<disk>/atomic_write_max_bytes
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
42 What: /sys/block/<disk>/atomic_write_unit_min_bytes
46 [RO] This parameter specifies the smallest block which can
50 atomic_write_unit_min. This value must be a power-of-two.
53 What: /sys/block/<disk>/atomic_write_unit_max_bytes
57 [RO] This parameter defines the largest block which can be
60 be a power-of-two. This value will not be larger than
64 What: /sys/block/<disk>/atomic_write_boundary_bytes
69 which straddles a given logical block address boundary. This
72 power-of-two and at least the size as in
78 What: /sys/block/<disk>/diskseq
82 The /sys/block/<disk>/diskseq files reports the disk
83 sequence number, which is a monotonically increasing
84 number assigned to every drive.
85 Some devices, like the loop device, refresh such number
90 What: /sys/block/<disk>/inflight
94 Reports the number of I/O requests currently in progress
96 than the number of requests queued in the block device queue.
100 Cf. Documentation/block/stat.rst which contains a single value for
102 This is related to /sys/block/<disk>/queue/nr_requests
106 What: /sys/block/<disk>/integrity/device_is_integrity_capable
111 integrity metadata. Set if the device is T10 PI-capable.
118 What: /sys/block/<disk>/integrity/format
122 Metadata format for integrity capable block device.
123 E.g. T10-DIF-TYPE1-CRC.
125 that the block device can send and receive.
133 What: /sys/block/<disk>/integrity/protection_interval_bytes
137 Describes the number of data bytes which are protected
139 block size.
142 What: /sys/block/<disk>/integrity/read_verify
146 Indicates whether the block layer should verify the
151 What: /sys/block/<disk>/integrity/tag_size
155 Number of bytes of integrity tag space available per
157 the device's logical block size.
162 space available for adding an opaque tag to each block
169 What: /sys/block/<disk>/integrity/write_generate
173 Indicates whether the block layer should automatically
178 What: /sys/block/<disk>/partscan
182 The /sys/block/<disk>/partscan files reports if partition
184 scanning is enabled, or "0" if not. The value type is a 32-bit
188 What: /sys/block/<disk>/<partition>/alignment_offset
192 Storage devices may report a physical block size that is
193 bigger than the logical block size (for instance a drive
194 with 4KB physical sectors exposing 512-byte logical
200 What: /sys/block/<disk>/<partition>/discard_alignment
206 the exported logical block size. The discard_alignment
212 What: /sys/block/<disk>/<partition>/stat
216 The /sys/block/<disk>/<partition>/stat files display the
218 same as the format of /sys/block/<disk>/stat.
221 What: /sys/block/<disk>/queue/add_random
223 Contact: linux-block@vger.kernel.org
229 What: /sys/block/<disk>/queue/chunk_sectors
234 of the disk. For a RAID device (dm-raid), chunk_sectors
236 segment. For a zoned block device, either host-aware or
237 host-managed, chunk_sectors indicates the size in 512B sectors
242 What: /sys/block/<disk>/queue/crypto/
244 Contact: linux-block@vger.kernel.org
246 The presence of this subdirectory of /sys/block/<disk>/queue/
250 encryption, refer to Documentation/block/inline-encryption.rst.
253 What: /sys/block/<disk>/queue/crypto/hw_wrapped_keys
255 Contact: linux-block@vger.kernel.org
258 supports hardware-wrapped inline encryption keys, i.e. key blobs
260 more information about hardware-wrapped inline encryption keys,
261 see Documentation/block/inline-encryption.rst.
264 What: /sys/block/<disk>/queue/crypto/max_dun_bits
266 Contact: linux-block@vger.kernel.org
272 What: /sys/block/<disk>/queue/crypto/modes/<mode>
274 Contact: linux-block@vger.kernel.org
279 number that is a bitmask of the supported data unit sizes, in
284 * AES-256-XTS
285 * AES-128-CBC-ESSIV
288 For example, if a device supports AES-256-XTS inline encryption
290 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
294 What: /sys/block/<disk>/queue/crypto/num_keyslots
296 Contact: linux-block@vger.kernel.org
298 [RO] This file shows the number of keyslots the device has for
302 What: /sys/block/<disk>/queue/crypto/raw_keys
304 Contact: linux-block@vger.kernel.org
311 What: /sys/block/<disk>/queue/dax
313 Contact: linux-block@vger.kernel.org
316 Access (DAX), used by CPU-addressable storage to bypass the
320 What: /sys/block/<disk>/queue/discard_granularity
326 block size. The discard_granularity parameter indicates the size
329 the device's physical block size. A discard_granularity of 0
333 What: /sys/block/<disk>/queue/discard_max_bytes
345 What: /sys/block/<disk>/queue/discard_max_hw_bytes
347 Contact: linux-block@vger.kernel.org
350 internal limits on the number of bytes that can be trimmed or
352 parameter is set by the device driver to the maximum number of
359 What: /sys/block/<disk>/queue/discard_zeroes_data
367 What: /sys/block/<disk>/queue/dma_alignment
369 Contact: linux-block@vger.kernel.org
372 used for raw block device access with O_DIRECT and other driver
376 What: /sys/block/<disk>/queue/fua
378 Contact: linux-block@vger.kernel.org
380 [RO] Whether or not the block driver supports the FUA flag for
386 What: /sys/block/<disk>/queue/hw_sector_size
388 Contact: linux-block@vger.kernel.org
393 What: /sys/block/<disk>/queue/independent_access_ranges/
395 Contact: linux-block@vger.kernel.org
397 [RO] The presence of this sub-directory of the
398 /sys/block/xxx/queue/ directory indicates that the device is
400 in parallel. For instance, single LUN multi-actuator hard-disks
408 number of sectors in the range starting from the first sector of
409 the range. For example, a dual-actuator hard-disk will have the
412 $ tree /sys/block/<disk>/queue/independent_access_ranges/
413 /sys/block/<disk>/queue/independent_access_ranges/
414 |-- 0
415 | |-- nr_sectors
416 | `-- sector
417 `-- 1
418 |-- nr_sectors
419 `-- sector
422 regardless of the actual block size of the device. Independent
429 What: /sys/block/<disk>/queue/io_poll
431 Contact: linux-block@vger.kernel.org
435 for this device. Writing any non-zero value will enable this
439 What: /sys/block/<disk>/queue/io_poll_delay
441 Contact: linux-block@vger.kernel.org
444 performed. It is now fixed to -1, which is classic polling.
450 What: /sys/block/<disk>/queue/io_timeout
455 request does not complete in this time then the block driver
461 What: /sys/block/<disk>/queue/iostats
463 Contact: linux-block@vger.kernel.org
468 What: /sys/block/<disk>/queue/iostats_passthrough
470 Contact: linux-block@vger.kernel.org
476 What: /sys/block/<disk>/queue/logical_block_size
484 What: /sys/block/<disk>/queue/max_active_zones
488 [RO] For zoned block devices (zoned attribute indicating
489 "host-managed" or "host-aware"), the sum of zones belonging to
498 What: /sys/block/<disk>/queue/max_discard_segments
500 Contact: linux-block@vger.kernel.org
502 [RO] The maximum number of DMA scatter/gather entries in a
506 What: /sys/block/<disk>/queue/max_hw_sectors_kb
508 Contact: linux-block@vger.kernel.org
510 [RO] This is the maximum number of kilobytes supported in a
514 What: /sys/block/<disk>/queue/max_integrity_segments
516 Contact: linux-block@vger.kernel.org
518 [RO] Maximum number of elements in a DMA scatter/gather list
519 with integrity data that will be submitted by the block layer
520 core to the associated block driver.
523 What: /sys/block/<disk>/queue/max_open_zones
527 [RO] For zoned block devices (zoned attribute indicating
528 "host-managed" or "host-aware"), the sum of zones belonging to
533 What: /sys/block/<disk>/queue/max_sectors_kb
535 Contact: linux-block@vger.kernel.org
537 [RW] This is the maximum number of kilobytes that the block
543 What: /sys/block/<disk>/queue/max_segment_size
545 Contact: linux-block@vger.kernel.org
550 What: /sys/block/<disk>/queue/max_write_streams
552 Contact: linux-block@vger.kernel.org
554 [RO] Maximum number of write streams supported, 0 if not
558 What: /sys/block/<disk>/queue/write_stream_granularity
560 Contact: linux-block@vger.kernel.org
566 What: /sys/block/<disk>/queue/max_segments
568 Contact: linux-block@vger.kernel.org
570 [RO] Maximum number of elements in a DMA scatter/gather list
571 that is submitted to the associated block driver.
574 What: /sys/block/<disk>/queue/minimum_io_size
581 drives this is often the physical block size. For RAID arrays
584 where a high number of I/O operations is desired.
587 What: /sys/block/<disk>/queue/nomerges
589 Contact: linux-block@vger.kernel.org
596 simple one-shot merges with the previous I/O request are
598 default value is 0 - which enables all types of merge tries.
601 What: /sys/block/<disk>/queue/nr_requests
603 Contact: linux-block@vger.kernel.org
606 block layer for read or write requests. Note that the total
607 allocated number may be twice this amount, since it applies only
613 each such per-block-cgroup request pool. IOW, if there are N
614 block cgroups, each request queue may have up to N request
618 What: /sys/block/<disk>/queue/nr_zones
622 [RO] nr_zones indicates the total number of zones of a zoned
623 block device ("host-aware" or "host-managed" zone model). For
624 regular block devices, the value is always 0.
627 What: /sys/block/<disk>/queue/optimal_io_size
640 What: /sys/block/<disk>/queue/physical_block_size
645 write atomically. It is usually the same as the logical block
647 sectors that expose a 512-byte logical block size to the
648 operating system. For stacked block devices the
653 What: /sys/block/<disk>/queue/read_ahead_kb
655 Contact: linux-block@vger.kernel.org
657 [RW] Maximum number of kilobytes to read-ahead for filesystems
658 on this block device.
664 What: /sys/block/<disk>/queue/rotational
666 Contact: linux-block@vger.kernel.org
669 type or non-rotational type.
672 What: /sys/block/<disk>/queue/rq_affinity
674 Contact: linux-block@vger.kernel.org
676 [RW] If this option is '1', the block layer will migrate request
687 What: /sys/block/<disk>/queue/scheduler
689 Contact: linux-block@vger.kernel.org
692 IO schedulers for this block device. The currently active IO
694 scheduler name to this file will switch control of this block
700 What: /sys/block/<disk>/queue/stable_writes
702 Contact: linux-block@vger.kernel.org
711 times where the same data must be seen every time -- for
716 What: /sys/block/<disk>/queue/virt_boundary_mask
718 Contact: linux-block@vger.kernel.org
721 the block device. I/O requests to this device will be split
728 What: /sys/block/<disk>/queue/wbt_lat_usec
730 Contact: linux-block@vger.kernel.org
737 value of '-1' to this file resets the value to the default
741 What: /sys/block/<disk>/queue/write_cache
743 Contact: linux-block@vger.kernel.org
755 What: /sys/block/<disk>/queue/write_same_max_bytes
760 single data block can be written to a range of several
768 What: /sys/block/<disk>/queue/write_zeroes_max_bytes
781 What: /sys/block/<disk>/queue/zone_append_max_bytes
783 Contact: linux-block@vger.kernel.org
785 [RO] This is the maximum number of bytes that can be written to
786 a sequential zone of a zoned block device using a zone append
788 regular block devices.
791 What: /sys/block/<disk>/queue/zone_write_granularity
793 Contact: linux-block@vger.kernel.org
796 write operations in sequential zones of zoned block devices
797 (devices with a zoned attributed that reports "host-managed" or
798 "host-aware"). This value is always 0 for regular block devices.
801 What: /sys/block/<disk>/queue/zoned
805 [RO] zoned indicates if the device is a zoned block device and
807 possible values indicated by zoned are "none" for regular block
808 devices and "host-aware" or "host-managed" for zoned block
809 devices. The characteristics of host-aware and host-managed
810 zoned block devices are described in the ZBC (Zoned Block
812 These standards also define the "drive-managed" zone model.
813 However, since drive-managed zoned block devices do not support
814 zone commands, they will be treated as regular block devices and
818 What: /sys/block/<disk>/hidden
820 Contact: linux-block@vger.kernel.org
822 [RO] the block device is hidden. it doesn’t produce events, and
827 What: /sys/block/<disk>/stat
831 The /sys/block/<disk>/stat files displays the I/O
854 For more details refer Documentation/admin-guide/iostats.rst