20
allows to tune the I/O elevator per blockdevice queue basis. The
21
tuning can be safely done at runtime. Tuning the elevator means
22
being able to change disk performance and interactiveness. In the
23
output of elvtune the address of the queue tuned will be shown
24
and it can be considered as a queue ID.
25
For example multiple partitions in the same harddisk will
20
allows to tune the I/O elevator per blockdevice queue. The
21
tuning can be safely done at runtime. Tuning the elevator means
22
being able to change disk performance and interactiveness.
25
the address of the queue tuned will be shown;
26
it can be considered as a queue ID.
27
Multiple partitions on the same harddisk will
26
28
share the same queue and so tuning one partition will be
27
29
like tuning the whole HD.
31
set the max latency that the I/O scheduler will provide on
33
Set the maximum latency that the I/O scheduler will provide on
35
set the max latency that the I/O scheduler will provide on
37
Set the maximum latency that the I/O scheduler will provide on
39
max coalescing factor allowed on writes when there are reads
41
Set the maximum coalescing factor allowed on writes when there are reads
40
42
pending in the queue.
45
Display help text and exit.
48
Display version version information and exit.
48
Actually the only fields tunable are those relative
49
to the IO scheduler. It's not possible to select
50
Actually, the only fields tunable are those relative
51
to the IO scheduler. It's not possible to select
50
52
a one-way or two-way elevator yet.
52
54
For logical blockdevices like LVM the tuning has to
55
devices. Tuning the queue of the LVM logical device
57
devices. Tuning the queue of the LVM logical device
58
60
0 on success and 1 on failure.