Home
last modified time | relevance | path

Searched refs:rotational (Results 1 – 7 of 7) sorted by relevance

/linux/Documentation/input/devices/
H A Drotary-encoder.rst50 rotational direction based on the last stable state. Events are reported in
/linux/drivers/block/null_blk/
H A Dmain.c270 module_param_named(rotational, g_rotational, bool, S_IRUGO);
271 MODULE_PARM_DESC(rotational, "Set the rotational feature for the device. Default: false");
484 NULLB_DEVICE_ATTR(rotational, bool, NULL);
838 dev->rotational = g_rotational; in null_alloc_dev()
2014 if (dev->rotational) in null_add_dev()
/linux/drivers/nvme/host/
H A Dnvme.h556 bool rotational; member
H A Dcore.c4048 head->rotational = info->is_rotational; in nvme_alloc_ns_head()
/linux/Documentation/block/
H A Dbfq-iosched.rst186 throughput on rotational devices and on non-queueing flash-based
459 on a non-rotational device, setting slice_idle to 0 may be needed too
/linux/Documentation/input/
H A Devent-codes.rst404 can report through the rotational axes (absolute and/or relative rx, ry, rz).
/linux/Documentation/admin-guide/
H A Dcgroup-v2.rst2275 workload. How a miss is detected depends on the device: on rotational devices
2277 non-rotational devices a miss is counted once enough of the IOs in the window
2296 idea of the latency you see during normal operation. On rotational devices,
2298 higher. On non-rotational devices io.stat reports no average latency; set
2343 report avg_lat and win; non-rotational devices report missed and total
2364 (Non-rotational devices only.) The number of IOs in the
2370 (Non-rotational devices only.) The total number of IOs