Eric Blake wrote:
On 02/17/2011 07:05 PM, Gui Jianfeng wrote:
> Documents for blkiotune.
>
> Signed-off-by: Gui Jianfeng <guijianfeng(a)cn.fujitsu.com>
> ---
> tools/virsh.pod | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/tools/virsh.pod b/tools/virsh.pod
> index a2ca384..014d953 100644
> --- a/tools/virsh.pod
> +++ b/tools/virsh.pod
> @@ -610,6 +610,10 @@ of 4MB, while 266240 (260MB) is valid without rounding.
> Note, to change the maximum memory allocation for a QEMU/KVM guest domain,
> use the virsh B<edit> command instead to update its XML <memory>
element.
>
> +=item B<blkiotune> I<domain-id> optional I<--weight>
B<weight>
> +
> +Display or set the blkio cgroup parameters. QEMU/KVM supports I<--weight>.
> +
Is it worth listing the range 100-1000? (Am I right on that range?)
Update it.
From: Gui Jianfeng <guijianfeng(a)cn.fujitsu.com>
Documents for blkiotune
Signed-off-by: Gui Jianfeng <guijianfeng(a)cn.fujitsu.com>
---
tools/virsh.pod | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/tools/virsh.pod b/tools/virsh.pod
index a2ca384..83a86af 100644
--- a/tools/virsh.pod
+++ b/tools/virsh.pod
@@ -610,6 +610,11 @@ of 4MB, while 266240 (260MB) is valid without rounding.
Note, to change the maximum memory allocation for a QEMU/KVM guest domain,
use the virsh B<edit> command instead to update its XML <memory> element.
+=item B<blkiotune> I<domain-id> optional I<--weight> B<weight>
+
+Display or set the blkio cgroup parameters. QEMU/KVM supports I<--weight>.
+I<--weight> is in range [100, 1000].
+
=item B<memtune> I<domain-id> optional I<--hard-limit>
B<kilobytes>
optional I<--soft-limit> B<kilobytes> optional I<--swap-hard-limit>
B<kilobytes> -I<--min-guarantee> B<kilobytes>
--
1.7.1