summaryrefslogtreecommitdiffstats
path: root/Documentation/block/null_blk.txt
diff options
context:
space:
mode:
authorMatias Bjorling <m@bjorling.me>2013-12-18 13:41:42 +0100
committerJens Axboe <axboe@kernel.dk>2013-12-19 08:09:41 -0700
commit12f8f4fc0314103d47f9b1cbc812597b8d893ce1 (patch)
treebdc15872255fd73cc1c118cda6cadd09ef0f41a1 /Documentation/block/null_blk.txt
parent0c56010c83703e1f33325838eda9a2077827b6f1 (diff)
downloadop-kernel-dev-12f8f4fc0314103d47f9b1cbc812597b8d893ce1.zip
op-kernel-dev-12f8f4fc0314103d47f9b1cbc812597b8d893ce1.tar.gz
null_blk: documentation
Add description of module and its parameters. Signed-off-by: Matias Bjorling <m@bjorling.me> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'Documentation/block/null_blk.txt')
-rw-r--r--Documentation/block/null_blk.txt71
1 files changed, 71 insertions, 0 deletions
diff --git a/Documentation/block/null_blk.txt b/Documentation/block/null_blk.txt
new file mode 100644
index 0000000..9e1b047
--- /dev/null
+++ b/Documentation/block/null_blk.txt
@@ -0,0 +1,71 @@
+Null block device driver
+================================================================================
+
+I. Overview
+
+The null block device (/dev/nullb*) is used for benchmarking the various
+block-layer implementations. It emulates a block device of X gigabytes in size.
+The following instances are possible:
+
+ Single-queue block-layer
+ - Request-based.
+ - Single submission queue per device.
+ - Implements IO scheduling algorithms (CFQ, Deadline, noop).
+ Multi-queue block-layer
+ - Request-based.
+ - Configurable submission queues per device.
+ No block-layer (Known as bio-based)
+ - Bio-based. IO requests are submitted directly to the device driver.
+ - Directly accepts bio data structure and returns them.
+
+All of them has a completion queue for each core in the system.
+
+II. Module parameters applicable for all instances:
+
+queue_mode=[0-2]: Default: 2-Multi-queue
+ Selects which block-layer the module should instantiate with.
+
+ 0: Bio-based.
+ 1: Single-queue.
+ 2: Multi-queue.
+
+home_node=[0--nr_nodes]: Default: NUMA_NO_NODE
+ Selects what socket the data structures is allocated from.
+
+gb=[Size in GB]: Default: 250GB
+ The size of the device reported to the system.
+
+bs=[Block size (in bytes)]: Default: 512 bytes
+ The block size reported to the system.
+
+nr_devices=[Num. devices]: Default: 2
+ Number of block devices instantiated. They are instantiated as /dev/nullb0,
+ etc.
+
+irq_mode=[0-2]: Default: Soft-irq
+ The completion mode used for completing IOs to the block-layer.
+
+ 0: None.
+ 1: Soft-irq. Uses ipi to complete IOs across sockets. Simulates the overhead
+ when IOs are issued from another socket than the home the device is
+ connected to.
+ 2: Timer: Waits a specific period (completion_nsec) for each IO before
+ completion.
+
+completion_nsec=[Num. ns]: Default: 10.000ns
+ Combined with irq_mode=2 (timer). The time each completion event must wait.
+
+submit_queues=[0..nr_cpus]:
+ The number of submission queues attached to the device driver. If unset, it
+ defaults to 1 on single-queue and bio-based instances. For multi-queue,
+ its ignored when use_per_node_hctx module parameter is 1.
+
+hw_queue_depth=[0..qdepth]: Defaults: 64
+ The hardware queue depth of the device.
+
+III: Multi-queue specific parameters
+
+use_per_node_hctx=[0/1]: Defaults: 1
+ If 1, the multi-queue block layer is instantiated with a hardware dispatch
+ queue for each CPU node in the system. If 0, it is instantiated with the
+ number of queues defined in the submit_queues parameter.
OpenPOWER on IntegriCloud