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>/<partition>/alignment_offset
108 Storage devices may report a physical block size that is
109 bigger than the logical block size (for instance a drive
116 What: /sys/block/<disk>/<partition>/discard_alignment
122 the exported logical block size. The discard_alignment
128 What: /sys/block/<disk>/<partition>/stat
132 The /sys/block/<disk>/<partition>/stat files display the
134 same as the format of /sys/block/<disk>/stat.
137 What: /sys/block/<disk>/queue/add_random
139 Contact: linux-block@vger.kernel.org
145 What: /sys/block/<disk>/queue/chunk_sectors
152 segment. For a zoned block device, either host-aware or
158 What: /sys/block/<disk>/queue/crypto/
160 Contact: linux-block@vger.kernel.org
162 The presence of this subdirectory of /sys/block/<disk>/queue/
166 encryption, refer to Documentation/block/inline-encryption.rst.
169 What: /sys/block/<disk>/queue/crypto/max_dun_bits
171 Contact: linux-block@vger.kernel.org
177 What: /sys/block/<disk>/queue/crypto/modes/<mode>
179 Contact: linux-block@vger.kernel.org
195 /sys/block/<disk>/queue/crypto/modes/AES-256-XTS will exist and
199 What: /sys/block/<disk>/queue/crypto/num_keyslots
201 Contact: linux-block@vger.kernel.org
207 What: /sys/block/<disk>/queue/dax
209 Contact: linux-block@vger.kernel.org
216 What: /sys/block/<disk>/queue/discard_granularity
222 block size. The discard_granularity parameter indicates the size
225 the device's physical block size. A discard_granularity of 0
229 What: /sys/block/<disk>/queue/discard_max_bytes
241 What: /sys/block/<disk>/queue/discard_max_hw_bytes
243 Contact: linux-block@vger.kernel.org
255 What: /sys/block/<disk>/queue/discard_zeroes_data
263 What: /sys/block/<disk>/queue/dma_alignment
265 Contact: linux-block@vger.kernel.org
268 used for raw block device access with O_DIRECT and other driver
272 What: /sys/block/<disk>/queue/fua
274 Contact: linux-block@vger.kernel.org
276 [RO] Whether or not the block driver supports the FUA flag for
282 What: /sys/block/<disk>/queue/hw_sector_size
284 Contact: linux-block@vger.kernel.org
289 What: /sys/block/<disk>/queue/independent_access_ranges/
291 Contact: linux-block@vger.kernel.org
294 /sys/block/xxx/queue/ directory indicates that the device is
308 $ tree /sys/block/<disk>/queue/independent_access_ranges/
309 /sys/block/<disk>/queue/independent_access_ranges/
318 regardless of the actual block size of the device. Independent
325 What: /sys/block/<disk>/queue/io_poll
327 Contact: linux-block@vger.kernel.org
335 What: /sys/block/<disk>/queue/io_poll_delay
337 Contact: linux-block@vger.kernel.org
353 What: /sys/block/<disk>/queue/io_timeout
358 request does not complete in this time then the block driver
364 What: /sys/block/<disk>/queue/iostats
366 Contact: linux-block@vger.kernel.org
372 What: /sys/block/<disk>/queue/logical_block_size
380 What: /sys/block/<disk>/queue/max_active_zones
384 [RO] For zoned block devices (zoned attribute indicating
394 What: /sys/block/<disk>/queue/max_discard_segments
396 Contact: linux-block@vger.kernel.org
402 What: /sys/block/<disk>/queue/max_hw_sectors_kb
404 Contact: linux-block@vger.kernel.org
410 What: /sys/block/<disk>/queue/max_integrity_segments
412 Contact: linux-block@vger.kernel.org
415 with integrity data that will be submitted by the block layer
416 core to the associated block driver.
419 What: /sys/block/<disk>/queue/max_open_zones
423 [RO] For zoned block devices (zoned attribute indicating
429 What: /sys/block/<disk>/queue/max_sectors_kb
431 Contact: linux-block@vger.kernel.org
433 [RW] This is the maximum number of kilobytes that the block
438 What: /sys/block/<disk>/queue/max_segment_size
440 Contact: linux-block@vger.kernel.org
446 What: /sys/block/<disk>/queue/max_segments
448 Contact: linux-block@vger.kernel.org
451 that is submitted to the associated block driver.
454 What: /sys/block/<disk>/queue/minimum_io_size
461 drives this is often the physical block size. For RAID arrays
467 What: /sys/block/<disk>/queue/nomerges
469 Contact: linux-block@vger.kernel.org
481 What: /sys/block/<disk>/queue/nr_requests
483 Contact: linux-block@vger.kernel.org
486 block layer for read or write requests. Note that the total
493 each such per-block-cgroup request pool. IOW, if there are N
494 block cgroups, each request queue may have up to N request
498 What: /sys/block/<disk>/queue/nr_zones
503 block device ("host-aware" or "host-managed" zone model). For
504 regular block devices, the value is always 0.
507 What: /sys/block/<disk>/queue/optimal_io_size
520 What: /sys/block/<disk>/queue/physical_block_size
525 write atomically. It is usually the same as the logical block
527 sectors that expose a 512-byte logical block size to the
528 operating system. For stacked block devices the
533 What: /sys/block/<disk>/queue/read_ahead_kb
535 Contact: linux-block@vger.kernel.org
538 on this block device.
541 What: /sys/block/<disk>/queue/rotational
543 Contact: linux-block@vger.kernel.org
549 What: /sys/block/<disk>/queue/rq_affinity
551 Contact: linux-block@vger.kernel.org
553 [RW] If this option is '1', the block layer will migrate request
564 What: /sys/block/<disk>/queue/scheduler
566 Contact: linux-block@vger.kernel.org
569 IO schedulers for this block device. The currently active IO
571 scheduler name to this file will switch control of this block
577 What: /sys/block/<disk>/queue/stable_writes
579 Contact: linux-block@vger.kernel.org
594 What: /sys/block/<disk>/queue/throttle_sample_time
596 Contact: linux-block@vger.kernel.org
605 What: /sys/block/<disk>/queue/virt_boundary_mask
607 Contact: linux-block@vger.kernel.org
610 the block device. I/O requests to this device will be split
617 What: /sys/block/<disk>/queue/wbt_lat_usec
619 Contact: linux-block@vger.kernel.org
630 What: /sys/block/<disk>/queue/write_cache
632 Contact: linux-block@vger.kernel.org
644 What: /sys/block/<disk>/queue/write_same_max_bytes
649 single data block can be written to a range of several
657 What: /sys/block/<disk>/queue/write_zeroes_max_bytes
670 What: /sys/block/<disk>/queue/zone_append_max_bytes
672 Contact: linux-block@vger.kernel.org
675 a sequential zone of a zoned block device using a zone append
677 regular block devices.
680 What: /sys/block/<disk>/queue/zone_write_granularity
682 Contact: linux-block@vger.kernel.org
685 write operations in sequential zones of zoned block devices
687 "host-aware"). This value is always 0 for regular block devices.
690 What: /sys/block/<disk>/queue/zoned
694 [RO] zoned indicates if the device is a zoned block device and
696 possible values indicated by zoned are "none" for regular block
697 devices and "host-aware" or "host-managed" for zoned block
699 zoned block devices are described in the ZBC (Zoned Block
702 However, since drive-managed zoned block devices do not support
703 zone commands, they will be treated as regular block devices and
707 What: /sys/block/<disk>/stat
711 The /sys/block/<disk>/stat files displays the I/O