On 11/23/2011 02:44 PM, Eric Blake wrote:
From: Lei Li <lilei(a)linux.vnet.ibm.com>
Enable block I/O throttle for per-disk in XML, as the first
per-disk IO tuning parameter.
Signed-off-by: Lei Li <lilei(a)linux.vnet.ibm.com>
Signed-off-by: Zhi Yong Wu <wuzhy(a)linux.vnet.ibm.com>
Signed-off-by: Eric Blake <eblake(a)redhat.com>
@@ -1039,6 +1044,40 @@
<span class="since">Since 0.0.3; <code>bus</code>
attribute since 0.4.3;
"usb" attribute value since after 0.4.4; "sata" attribute
value since
0.9.7</span></dd>
+ <dt><code>iotune</code></dt>
+ <dd>The optional <code>iotune</code> element provides the
+ ability to provide additional per-device I/O tuning, with
+ values that can vary for each device (contrast this to
+ the <a
href="#elementsBlockTuning"><code><blkiotune></code></a>
+ element, which applies globally to the domain).
I added a cross-reference in one direction, but not the other, so I'll
squash this in:
diff --git i/docs/formatdomain.html.in w/docs/formatdomain.html.in
index 933072e..f08b948 100644
--- i/docs/formatdomain.html.in
+++ w/docs/formatdomain.html.in
@@ -536,7 +536,11 @@
single host block device, if they are backed by files within
the same host file system, which is why this tuning parameter
is at the global domain level rather than associated with each
- guest disk device. Each <code>device</code> element has two
+ guest disk device (contrast this to
+ the <a
href="#elementsDisks"><code><iotune></code></a>
+ element which can apply to an
+ individual <code><disk></code>).
+ Each <code>device</code> element has two
mandatory sub-elements, <code>path</code> describing the
absolute path of the device, and <code>weight</code> giving
the relative weight of that device, in the range [100,
--
Eric Blake eblake(a)redhat.com +1-919-301-3266
Libvirt virtualization library
http://libvirt.org