Lines Matching +full:per +full:- +full:queue
7 with 4KB physical sectors exposing 512-byte logical
35 power-of-two and atomic_write_unit_max_bytes may also be
36 limited by some other queue limits, such as max_segments.
37 This parameter - along with atomic_write_unit_min_bytes
38 and atomic_write_unit_max_bytes - will not be larger than
50 atomic_write_unit_min. This value must be a power-of-two.
60 be a power-of-two. This value will not be larger than
72 power-of-two and at least the size as in
96 than the number of requests queued in the block device queue.
102 This is related to /sys/block/<disk>/queue/nr_requests
111 integrity metadata. Set if the device is T10 PI-capable.
119 E.g. T10-DIF-TYPE1-CRC.
144 Number of bytes of integrity tag space available per
163 scanning is enabled, or "0" if not. The value type is a 32-bit
173 with 4KB physical sectors exposing 512-byte logical
200 What: /sys/block/<disk>/queue/add_random
202 Contact: linux-block@vger.kernel.org
208 What: /sys/block/<disk>/queue/chunk_sectors
213 of the disk. For a RAID device (dm-raid), chunk_sectors
215 segment. For a zoned block device, either host-aware or
216 host-managed, chunk_sectors indicates the size in 512B sectors
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
252 * AES-256-XTS
253 * AES-128-CBC-ESSIV
256 For example, if a device supports AES-256-XTS inline encryption
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
275 Access (DAX), used by CPU-addressable storage to bypass the
279 What: /sys/block/<disk>/queue/discard_granularity
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
335 What: /sys/block/<disk>/queue/fua
337 Contact: linux-block@vger.kernel.org
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
356 [RO] The presence of this sub-directory of the
357 /sys/block/xxx/queue/ directory indicates that the device is
359 in parallel. For instance, single LUN multi-actuator hard-disks
364 per access range, with each range described using the sector
368 the range. For example, a dual-actuator hard-disk will have the
371 $ tree /sys/block/<disk>/queue/independent_access_ranges/
372 /sys/block/<disk>/queue/independent_access_ranges/
373 |-- 0
374 | |-- nr_sectors
375 | `-- sector
376 `-- 1
377 |-- nr_sectors
378 `-- sector
388 What: /sys/block/<disk>/queue/io_poll
390 Contact: linux-block@vger.kernel.org
394 for this device. Writing any non-zero value will enable this
398 What: /sys/block/<disk>/queue/io_poll_delay
400 Contact: linux-block@vger.kernel.org
403 performed. It is now fixed to -1, which is classic polling.
409 What: /sys/block/<disk>/queue/io_timeout
420 What: /sys/block/<disk>/queue/iostats
422 Contact: linux-block@vger.kernel.org
428 What: /sys/block/<disk>/queue/logical_block_size
436 What: /sys/block/<disk>/queue/max_active_zones
441 "host-managed" or "host-aware"), the sum of zones belonging to
450 What: /sys/block/<disk>/queue/max_discard_segments
452 Contact: linux-block@vger.kernel.org
458 What: /sys/block/<disk>/queue/max_hw_sectors_kb
460 Contact: linux-block@vger.kernel.org
466 What: /sys/block/<disk>/queue/max_integrity_segments
468 Contact: linux-block@vger.kernel.org
475 What: /sys/block/<disk>/queue/max_open_zones
480 "host-managed" or "host-aware"), the sum of zones belonging to
485 What: /sys/block/<disk>/queue/max_sectors_kb
487 Contact: linux-block@vger.kernel.org
495 What: /sys/block/<disk>/queue/max_segment_size
497 Contact: linux-block@vger.kernel.org
503 What: /sys/block/<disk>/queue/max_segments
505 Contact: linux-block@vger.kernel.org
511 What: /sys/block/<disk>/queue/minimum_io_size
524 What: /sys/block/<disk>/queue/nomerges
526 Contact: linux-block@vger.kernel.org
533 simple one-shot merges with the previous I/O request are
535 default value is 0 - which enables all types of merge tries.
538 What: /sys/block/<disk>/queue/nr_requests
540 Contact: linux-block@vger.kernel.org
548 request queue maintains a separate request pool per each cgroup
550 each such per-block-cgroup request pool. IOW, if there are N
551 block cgroups, each request queue may have up to N request
555 What: /sys/block/<disk>/queue/nr_zones
560 block device ("host-aware" or "host-managed" zone model). For
564 What: /sys/block/<disk>/queue/optimal_io_size
577 What: /sys/block/<disk>/queue/physical_block_size
584 sectors that expose a 512-byte logical block size to the
590 What: /sys/block/<disk>/queue/read_ahead_kb
592 Contact: linux-block@vger.kernel.org
594 [RW] Maximum number of kilobytes to read-ahead for filesystems
601 What: /sys/block/<disk>/queue/rotational
603 Contact: linux-block@vger.kernel.org
606 type or non-rotational type.
609 What: /sys/block/<disk>/queue/rq_affinity
611 Contact: linux-block@vger.kernel.org
624 What: /sys/block/<disk>/queue/scheduler
626 Contact: linux-block@vger.kernel.org
637 What: /sys/block/<disk>/queue/stable_writes
639 Contact: linux-block@vger.kernel.org
648 times where the same data must be seen every time -- for
653 What: /sys/block/<disk>/queue/virt_boundary_mask
655 Contact: linux-block@vger.kernel.org
665 What: /sys/block/<disk>/queue/wbt_lat_usec
667 Contact: linux-block@vger.kernel.org
674 value of '-1' to this file resets the value to the default
678 What: /sys/block/<disk>/queue/write_cache
680 Contact: linux-block@vger.kernel.org
692 What: /sys/block/<disk>/queue/write_same_max_bytes
705 What: /sys/block/<disk>/queue/write_zeroes_max_bytes
718 What: /sys/block/<disk>/queue/zone_append_max_bytes
720 Contact: linux-block@vger.kernel.org
728 What: /sys/block/<disk>/queue/zone_write_granularity
730 Contact: linux-block@vger.kernel.org
734 (devices with a zoned attributed that reports "host-managed" or
735 "host-aware"). This value is always 0 for regular block devices.
738 What: /sys/block/<disk>/queue/zoned
745 devices and "host-aware" or "host-managed" for zoned block
746 devices. The characteristics of host-aware and host-managed
749 These standards also define the "drive-managed" zone model.
750 However, since drive-managed zoned block devices do not support
757 Contact: linux-block@vger.kernel.org
791 For more details refer Documentation/admin-guide/iostats.rst