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
25 What: /sys/block/<disk>/diskseq
29 The /sys/block/<disk>/diskseq files reports the disk
37 What: /sys/block/<disk>/inflight
43 than the number of requests queued in the block device queue.
47 Cf. Documentation/block/stat.rst which contains a single value for
49 This is related to /sys/block/<disk>/queue/nr_requests
53 What: /sys/block/<disk>/integrity/device_is_integrity_capable
61 What: /sys/block/<disk>/integrity/format
65 Metadata format for integrity capable block device.
69 What: /sys/block/<disk>/integrity/protection_interval_bytes
75 block size.
78 What: /sys/block/<disk>/integrity/read_verify
82 Indicates whether the block layer should verify the
87 What: /sys/block/<disk>/integrity/tag_size
95 What: /sys/block/<disk>/integrity/write_generate
99 Indicates whether the block layer should automatically
104 What: /sys/block/<disk>/partscan
108 The /sys/block/<disk>/partscan files reports if partition
114 What: /sys/block/<disk>/<partition>/alignment_offset
118 Storage devices may report a physical block size that is
119 bigger than the logical block size (for instance a drive
126 What: /sys/block/<disk>/<partition>/discard_alignment
132 the exported logical block size. The discard_alignment
138 What: /sys/block/<disk>/<partition>/stat
142 The /sys/block/<disk>/<partition>/stat files display the
144 same as the format of /sys/block/<disk>/stat.
147 What: /sys/block/<disk>/queue/add_random
149 Contact: linux-block@vger.kernel.org
155 What: /sys/block/<disk>/queue/chunk_sectors
162 segment. For a zoned block device, either host-aware or
168 What: /sys/block/<disk>/queue/crypto/
170 Contact: linux-block@vger.kernel.org
172 The presence of this subdirectory of /sys/block/<disk>/queue/
176 encryption, refer to Documentation/block/inline-encryption.rst.
179 What: /sys/block/<disk>/queue/crypto/max_dun_bits
181 Contact: linux-block@vger.kernel.org
187 What: /sys/block/<disk>/queue/crypto/modes/<mode>
189 Contact: linux-block@vger.kernel.org
205 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
209 What: /sys/block/<disk>/queue/crypto/num_keyslots
211 Contact: linux-block@vger.kernel.org
217 What: /sys/block/<disk>/queue/dax
219 Contact: linux-block@vger.kernel.org
226 What: /sys/block/<disk>/queue/discard_granularity
232 block size. The discard_granularity parameter indicates the size
235 the device's physical block size. A discard_granularity of 0
239 What: /sys/block/<disk>/queue/discard_max_bytes
251 What: /sys/block/<disk>/queue/discard_max_hw_bytes
253 Contact: linux-block@vger.kernel.org
265 What: /sys/block/<disk>/queue/discard_zeroes_data
273 What: /sys/block/<disk>/queue/dma_alignment
275 Contact: linux-block@vger.kernel.org
278 used for raw block device access with O_DIRECT and other driver
282 What: /sys/block/<disk>/queue/fua
284 Contact: linux-block@vger.kernel.org
286 [RO] Whether or not the block driver supports the FUA flag for
292 What: /sys/block/<disk>/queue/hw_sector_size
294 Contact: linux-block@vger.kernel.org
299 What: /sys/block/<disk>/queue/independent_access_ranges/
301 Contact: linux-block@vger.kernel.org
304 /sys/block/xxx/queue/ directory indicates that the device is
318 $ tree /sys/block/<disk>/queue/independent_access_ranges/
319 /sys/block/<disk>/queue/independent_access_ranges/
328 regardless of the actual block size of the device. Independent
335 What: /sys/block/<disk>/queue/io_poll
337 Contact: linux-block@vger.kernel.org
345 What: /sys/block/<disk>/queue/io_poll_delay
347 Contact: linux-block@vger.kernel.org
356 What: /sys/block/<disk>/queue/io_timeout
361 request does not complete in this time then the block driver
367 What: /sys/block/<disk>/queue/iostats
369 Contact: linux-block@vger.kernel.org
375 What: /sys/block/<disk>/queue/logical_block_size
383 What: /sys/block/<disk>/queue/max_active_zones
387 [RO] For zoned block devices (zoned attribute indicating
397 What: /sys/block/<disk>/queue/max_discard_segments
399 Contact: linux-block@vger.kernel.org
405 What: /sys/block/<disk>/queue/max_hw_sectors_kb
407 Contact: linux-block@vger.kernel.org
413 What: /sys/block/<disk>/queue/max_integrity_segments
415 Contact: linux-block@vger.kernel.org
418 with integrity data that will be submitted by the block layer
419 core to the associated block driver.
422 What: /sys/block/<disk>/queue/max_open_zones
426 [RO] For zoned block devices (zoned attribute indicating
432 What: /sys/block/<disk>/queue/max_sectors_kb
434 Contact: linux-block@vger.kernel.org
436 [RW] This is the maximum number of kilobytes that the block
442 What: /sys/block/<disk>/queue/max_segment_size
444 Contact: linux-block@vger.kernel.org
450 What: /sys/block/<disk>/queue/max_segments
452 Contact: linux-block@vger.kernel.org
455 that is submitted to the associated block driver.
458 What: /sys/block/<disk>/queue/minimum_io_size
465 drives this is often the physical block size. For RAID arrays
471 What: /sys/block/<disk>/queue/nomerges
473 Contact: linux-block@vger.kernel.org
485 What: /sys/block/<disk>/queue/nr_requests
487 Contact: linux-block@vger.kernel.org
490 block layer for read or write requests. Note that the total
497 each such per-block-cgroup request pool. IOW, if there are N
498 block cgroups, each request queue may have up to N request
502 What: /sys/block/<disk>/queue/nr_zones
507 block device ("host-aware" or "host-managed" zone model). For
508 regular block devices, the value is always 0.
511 What: /sys/block/<disk>/queue/optimal_io_size
524 What: /sys/block/<disk>/queue/physical_block_size
529 write atomically. It is usually the same as the logical block
531 sectors that expose a 512-byte logical block size to the
532 operating system. For stacked block devices the
537 What: /sys/block/<disk>/queue/read_ahead_kb
539 Contact: linux-block@vger.kernel.org
542 on this block device.
545 What: /sys/block/<disk>/queue/rotational
547 Contact: linux-block@vger.kernel.org
553 What: /sys/block/<disk>/queue/rq_affinity
555 Contact: linux-block@vger.kernel.org
557 [RW] If this option is '1', the block layer will migrate request
568 What: /sys/block/<disk>/queue/scheduler
570 Contact: linux-block@vger.kernel.org
573 IO schedulers for this block device. The currently active IO
575 scheduler name to this file will switch control of this block
581 What: /sys/block/<disk>/queue/stable_writes
583 Contact: linux-block@vger.kernel.org
598 What: /sys/block/<disk>/queue/throttle_sample_time
600 Contact: linux-block@vger.kernel.org
609 What: /sys/block/<disk>/queue/virt_boundary_mask
611 Contact: linux-block@vger.kernel.org
614 the block device. I/O requests to this device will be split
621 What: /sys/block/<disk>/queue/wbt_lat_usec
623 Contact: linux-block@vger.kernel.org
634 What: /sys/block/<disk>/queue/write_cache
636 Contact: linux-block@vger.kernel.org
648 What: /sys/block/<disk>/queue/write_same_max_bytes
653 single data block can be written to a range of several
661 What: /sys/block/<disk>/queue/write_zeroes_max_bytes
674 What: /sys/block/<disk>/queue/zone_append_max_bytes
676 Contact: linux-block@vger.kernel.org
679 a sequential zone of a zoned block device using a zone append
681 regular block devices.
684 What: /sys/block/<disk>/queue/zone_write_granularity
686 Contact: linux-block@vger.kernel.org
689 write operations in sequential zones of zoned block devices
691 "host-aware"). This value is always 0 for regular block devices.
694 What: /sys/block/<disk>/queue/zoned
698 [RO] zoned indicates if the device is a zoned block device and
700 possible values indicated by zoned are "none" for regular block
701 devices and "host-aware" or "host-managed" for zoned block
703 zoned block devices are described in the ZBC (Zoned Block
706 However, since drive-managed zoned block devices do not support
707 zone commands, they will be treated as regular block devices and
711 What: /sys/block/<disk>/hidden
713 Contact: linux-block@vger.kernel.org
715 [RO] the block device is hidden. it doesn’t produce events, and
720 What: /sys/block/<disk>/stat
724 The /sys/block/<disk>/stat files displays the I/O