Lines Matching full:block
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
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
42 What: /sys/block/<disk>/atomic_write_unit_min_bytes
46 [RO] This parameter specifies the smallest block which can
53 What: /sys/block/<disk>/atomic_write_unit_max_bytes
57 [RO] This parameter defines the largest block which can be
64 What: /sys/block/<disk>/atomic_write_boundary_bytes
69 which straddles a given logical block address boundary. This
78 What: /sys/block/<disk>/diskseq
82 The /sys/block/<disk>/diskseq files reports the disk
90 What: /sys/block/<disk>/inflight
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
114 What: /sys/block/<disk>/integrity/format
118 Metadata format for integrity capable block device.
122 What: /sys/block/<disk>/integrity/protection_interval_bytes
128 block size.
131 What: /sys/block/<disk>/integrity/read_verify
135 Indicates whether the block layer should verify the
140 What: /sys/block/<disk>/integrity/tag_size
148 What: /sys/block/<disk>/integrity/write_generate
152 Indicates whether the block layer should automatically
157 What: /sys/block/<disk>/partscan
161 The /sys/block/<disk>/partscan files reports if partition
167 What: /sys/block/<disk>/<partition>/alignment_offset
171 Storage devices may report a physical block size that is
172 bigger than the logical block size (for instance a drive
179 What: /sys/block/<disk>/<partition>/discard_alignment
185 the exported logical block size. The discard_alignment
191 What: /sys/block/<disk>/<partition>/stat
195 The /sys/block/<disk>/<partition>/stat files display the
197 same as the format of /sys/block/<disk>/stat.
200 What: /sys/block/<disk>/queue/add_random
202 Contact: linux-block@vger.kernel.org
208 What: /sys/block/<disk>/queue/chunk_sectors
215 segment. For a zoned block device, either host-aware or
221 What: /sys/block/<disk>/queue/crypto/
223 Contact: linux-block@vger.kernel.org
225 The presence of this subdirectory of /sys/block/<disk>/queue/
229 encryption, refer to Documentation/block/inline-encryption.rst.
232 What: /sys/block/<disk>/queue/crypto/max_dun_bits
234 Contact: linux-block@vger.kernel.org
240 What: /sys/block/<disk>/queue/crypto/modes/<mode>
242 Contact: linux-block@vger.kernel.org
258 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
262 What: /sys/block/<disk>/queue/crypto/num_keyslots
264 Contact: linux-block@vger.kernel.org
270 What: /sys/block/<disk>/queue/dax
272 Contact: linux-block@vger.kernel.org
279 What: /sys/block/<disk>/queue/discard_granularity
285 block size. The discard_granularity parameter indicates the size
288 the device's physical block size. A discard_granularity of 0
292 What: /sys/block/<disk>/queue/discard_max_bytes
304 What: /sys/block/<disk>/queue/discard_max_hw_bytes
306 Contact: linux-block@vger.kernel.org
318 What: /sys/block/<disk>/queue/discard_zeroes_data
326 What: /sys/block/<disk>/queue/dma_alignment
328 Contact: linux-block@vger.kernel.org
331 used for raw block device access with O_DIRECT and other driver
335 What: /sys/block/<disk>/queue/fua
337 Contact: linux-block@vger.kernel.org
339 [RO] Whether or not the block driver supports the FUA flag for
345 What: /sys/block/<disk>/queue/hw_sector_size
347 Contact: linux-block@vger.kernel.org
352 What: /sys/block/<disk>/queue/independent_access_ranges/
354 Contact: linux-block@vger.kernel.org
357 /sys/block/xxx/queue/ directory indicates that the device is
371 $ tree /sys/block/<disk>/queue/independent_access_ranges/
372 /sys/block/<disk>/queue/independent_access_ranges/
381 regardless of the actual block size of the device. Independent
388 What: /sys/block/<disk>/queue/io_poll
390 Contact: linux-block@vger.kernel.org
398 What: /sys/block/<disk>/queue/io_poll_delay
400 Contact: linux-block@vger.kernel.org
409 What: /sys/block/<disk>/queue/io_timeout
414 request does not complete in this time then the block driver
420 What: /sys/block/<disk>/queue/iostats
422 Contact: linux-block@vger.kernel.org
427 What: /sys/block/<disk>/queue/iostats_passthrough
429 Contact: linux-block@vger.kernel.org
435 What: /sys/block/<disk>/queue/logical_block_size
443 What: /sys/block/<disk>/queue/max_active_zones
447 [RO] For zoned block devices (zoned attribute indicating
457 What: /sys/block/<disk>/queue/max_discard_segments
459 Contact: linux-block@vger.kernel.org
465 What: /sys/block/<disk>/queue/max_hw_sectors_kb
467 Contact: linux-block@vger.kernel.org
473 What: /sys/block/<disk>/queue/max_integrity_segments
475 Contact: linux-block@vger.kernel.org
478 with integrity data that will be submitted by the block layer
479 core to the associated block driver.
482 What: /sys/block/<disk>/queue/max_open_zones
486 [RO] For zoned block devices (zoned attribute indicating
492 What: /sys/block/<disk>/queue/max_sectors_kb
494 Contact: linux-block@vger.kernel.org
496 [RW] This is the maximum number of kilobytes that the block
502 What: /sys/block/<disk>/queue/max_segment_size
504 Contact: linux-block@vger.kernel.org
510 What: /sys/block/<disk>/queue/max_segments
512 Contact: linux-block@vger.kernel.org
515 that is submitted to the associated block driver.
518 What: /sys/block/<disk>/queue/minimum_io_size
525 drives this is often the physical block size. For RAID arrays
531 What: /sys/block/<disk>/queue/nomerges
533 Contact: linux-block@vger.kernel.org
545 What: /sys/block/<disk>/queue/nr_requests
547 Contact: linux-block@vger.kernel.org
550 block layer for read or write requests. Note that the total
557 each such per-block-cgroup request pool. IOW, if there are N
558 block cgroups, each request queue may have up to N request
562 What: /sys/block/<disk>/queue/nr_zones
567 block device ("host-aware" or "host-managed" zone model). For
568 regular block devices, the value is always 0.
571 What: /sys/block/<disk>/queue/optimal_io_size
584 What: /sys/block/<disk>/queue/physical_block_size
589 write atomically. It is usually the same as the logical block
591 sectors that expose a 512-byte logical block size to the
592 operating system. For stacked block devices the
597 What: /sys/block/<disk>/queue/read_ahead_kb
599 Contact: linux-block@vger.kernel.org
602 on this block device.
608 What: /sys/block/<disk>/queue/rotational
610 Contact: linux-block@vger.kernel.org
616 What: /sys/block/<disk>/queue/rq_affinity
618 Contact: linux-block@vger.kernel.org
620 [RW] If this option is '1', the block layer will migrate request
631 What: /sys/block/<disk>/queue/scheduler
633 Contact: linux-block@vger.kernel.org
636 IO schedulers for this block device. The currently active IO
638 scheduler name to this file will switch control of this block
644 What: /sys/block/<disk>/queue/stable_writes
646 Contact: linux-block@vger.kernel.org
660 What: /sys/block/<disk>/queue/virt_boundary_mask
662 Contact: linux-block@vger.kernel.org
665 the block device. I/O requests to this device will be split
672 What: /sys/block/<disk>/queue/wbt_lat_usec
674 Contact: linux-block@vger.kernel.org
685 What: /sys/block/<disk>/queue/write_cache
687 Contact: linux-block@vger.kernel.org
699 What: /sys/block/<disk>/queue/write_same_max_bytes
704 single data block can be written to a range of several
712 What: /sys/block/<disk>/queue/write_zeroes_max_bytes
725 What: /sys/block/<disk>/queue/zone_append_max_bytes
727 Contact: linux-block@vger.kernel.org
730 a sequential zone of a zoned block device using a zone append
732 regular block devices.
735 What: /sys/block/<disk>/queue/zone_write_granularity
737 Contact: linux-block@vger.kernel.org
740 write operations in sequential zones of zoned block devices
742 "host-aware"). This value is always 0 for regular block devices.
745 What: /sys/block/<disk>/queue/zoned
749 [RO] zoned indicates if the device is a zoned block device and
751 possible values indicated by zoned are "none" for regular block
752 devices and "host-aware" or "host-managed" for zoned block
754 zoned block devices are described in the ZBC (Zoned Block
757 However, since drive-managed zoned block devices do not support
758 zone commands, they will be treated as regular block devices and
762 What: /sys/block/<disk>/hidden
764 Contact: linux-block@vger.kernel.org
766 [RO] the block device is hidden. it doesn’t produce events, and
771 What: /sys/block/<disk>/stat
775 The /sys/block/<disk>/stat files displays the I/O