Lines Matching +full:blocking +full:- +full:io

1 .. SPDX-License-Identifier: GPL-2.0
11 block-layer implementations. It emulates a block device of X gigabytes in size.
15   Multi-queue block-layer
17     - Request-based.
18     - Configurable submission queues per device.
20   No block-layer (Known as bio-based)
22     - Bio-based. IO requests are submitted directly to the device driver.
23     - Directly accepts bio data structure and returns them.
30 queue_mode=[0-2]: Default: 2-Multi-queue
31   Selects which block-layer the module should instantiate with.
34   0  Bio-based
35   1  Single-queue (deprecated)
36   2  Multi-queue
39 home_node=[0--nr_nodes]: Default: NUMA_NO_NODE
52 irqmode=[0-2]: Default: 1-Soft-irq
53   The completion mode used for completing IOs to the block-layer.
57   1  Soft-irq. Uses IPI to complete IOs across CPU nodes. Simulates the overhead
60   2  Timer: Waits a specific period (completion_nsec) for each IO before
69   defaults to 1. For multi-queue, it is ignored when use_per_node_hctx module
75 Multi-queue specific parameters
76 -------------------------------
84   1  The multi-queue block layer is instantiated with a hardware dispatch
89   Enable/disable the io scheduler.
92   0  nullb* use default blk-mq io scheduler
93   1  nullb* doesn't use io scheduler
96 blocking=[0/1]: Default: 0
97   Blocking behavior of the request queue.
100   0  Register as a non-blocking blk-mq driver device.
101   1  Register as a blocking blk-mq driver device, null_blk will set
103      needs to block in its ->queue_rq() function.
111   1  Tag set shared between devices for blk-mq. Only makes sense with
116   Device is a random-access or a zoned block device.
119   0  Block device is exposed as a random-access block device.
120   1  Block device is exposed as a host-managed zoned block device. Requires
129   zone_nr_conv >= nr_zones, it will be reduced to nr_zones - 1.