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
118 What: /sys/block/<disk>/integrity/format
122 Metadata format for integrity capable block device.
125 that the block device can send and receive.
133 What: /sys/block/<disk>/integrity/protection_interval_bytes
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
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
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
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
236 segment. For a zoned block device, either host-aware or
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
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
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
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
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
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
398 /sys/block/xxx/queue/ directory indicates that the device is
412 $ tree /sys/block/<disk>/queue/independent_access_ranges/
413 /sys/block/<disk>/queue/independent_access_ranges/
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
439 What: /sys/block/<disk>/queue/io_poll_delay
441 Contact: linux-block@vger.kernel.org
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
498 What: /sys/block/<disk>/queue/max_discard_segments
500 Contact: linux-block@vger.kernel.org
506 What: /sys/block/<disk>/queue/max_hw_sectors_kb
508 Contact: linux-block@vger.kernel.org
514 What: /sys/block/<disk>/queue/max_integrity_segments
516 Contact: linux-block@vger.kernel.org
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
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
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
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
587 What: /sys/block/<disk>/queue/nomerges
589 Contact: linux-block@vger.kernel.org
601 What: /sys/block/<disk>/queue/nr_requests
603 Contact: linux-block@vger.kernel.org
606 block layer. Noted this value only represents the quantity for a
612 What: /sys/block/<disk>/queue/async_depth
614 Contact: linux-block@vger.kernel.org
617 in the block layer. The value is always capped at nr_requests.
657 What: /sys/block/<disk>/queue/nr_zones
662 block device ("host-aware" or "host-managed" zone model). For
663 regular block devices, the value is always 0.
666 What: /sys/block/<disk>/queue/optimal_io_size
679 What: /sys/block/<disk>/queue/physical_block_size
684 write atomically. It is usually the same as the logical block
686 sectors that expose a 512-byte logical block size to the
687 operating system. For stacked block devices the
692 What: /sys/block/<disk>/queue/read_ahead_kb
694 Contact: linux-block@vger.kernel.org
697 on this block device.
703 What: /sys/block/<disk>/queue/rotational
705 Contact: linux-block@vger.kernel.org
711 What: /sys/block/<disk>/queue/rq_affinity
713 Contact: linux-block@vger.kernel.org
715 [RW] If this option is '1', the block layer will migrate request
726 What: /sys/block/<disk>/queue/scheduler
728 Contact: linux-block@vger.kernel.org
731 IO schedulers for this block device. The currently active IO
733 scheduler name to this file will switch control of this block
739 What: /sys/block/<disk>/queue/stable_writes
741 Contact: linux-block@vger.kernel.org
755 What: /sys/block/<disk>/queue/virt_boundary_mask
757 Contact: linux-block@vger.kernel.org
760 the block device. I/O requests to this device will be split
767 What: /sys/block/<disk>/queue/wbt_lat_usec
769 Contact: linux-block@vger.kernel.org
780 What: /sys/block/<disk>/queue/write_cache
782 Contact: linux-block@vger.kernel.org
794 What: /sys/block/<disk>/queue/write_same_max_bytes
799 single data block can be written to a range of several
807 What: /sys/block/<disk>/queue/write_zeroes_max_bytes
820 What: /sys/block/<disk>/queue/write_zeroes_unmap_max_hw_bytes
825 in a specified block range without incurring the cost of
827 block. If this parameter is set to write_zeroes_max_bytes, the
830 subsequent reads from the specified block range will return
834 clear a block range smaller than the device's internal
836 have to write each logical block media during a zeroing
840 What: /sys/block/<disk>/queue/write_zeroes_unmap_max_bytes
853 What: /sys/block/<disk>/queue/zone_append_max_bytes
855 Contact: linux-block@vger.kernel.org
858 a sequential zone of a zoned block device using a zone append
860 regular block devices.
863 What: /sys/block/<disk>/queue/zone_write_granularity
865 Contact: linux-block@vger.kernel.org
868 write operations in sequential zones of zoned block devices
870 "host-aware"). This value is always 0 for regular block devices.
873 What: /sys/block/<disk>/queue/zoned
877 [RO] zoned indicates if the device is a zoned block device and
879 possible values indicated by zoned are "none" for regular block
880 devices and "host-aware" or "host-managed" for zoned block
882 zoned block devices are described in the ZBC (Zoned Block
885 However, since drive-managed zoned block devices do not support
886 zone commands, they will be treated as regular block devices and
890 What: /sys/block/<disk>/hidden
892 Contact: linux-block@vger.kernel.org
894 [RO] the block device is hidden. it doesn’t produce events, and
899 What: /sys/block/<disk>/stat
903 The /sys/block/<disk>/stat files displays the I/O