All of lore.kernel.org
 help / color / mirror / Atom feed
From: shu ming <shuming@linux.vnet.ibm.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: libvir-list@redhat.com, guijianfeng@cn.fujitsu.com,
	QEMU Developers <qemu-devel@nongnu.org>,
	hutao@cn.fujitsu.com
Subject: Re: [Qemu-devel] [libvirt] The design choice for how to enable block I/O throttling function in libvirt
Date: Tue, 30 Aug 2011 16:31:44 +0800	[thread overview]
Message-ID: <4E5C9FF0.5020206@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAEH94LipqTEEvcwZ9w07Nt4p-xTV6ciusz+NBEpwhfti2JZbaA@mail.gmail.com>

Zhi Yong Wu:
> On Tue, Aug 30, 2011 at 3:18 PM, shu ming<shuming@linux.vnet.ibm.com>  wrote:
>> See commens below.
>> Zhi Yong Wu:
>>> HI, folks,
>>>
>>> I am trying to enable block I/O throttling function in libvirt. But
>>> currently i met some design questions, and don't make sure if we
>>> should extend blkiotune to support block I/O throttling or introduce
>>> one new libvirt command "blkiothrottle" to cover it or not. If you
>>> have some better idea, pls don't hesitate to drop your comments.
>>>
>>> If one new libvirt command "blkiothrottle" is introduced, I plan to
>>> design its usage syntax as below:
>>>
>>> virsh # help blkiothrottle
>>>    NAME
>>>      blkiothrottle - Set or display a block disk I/O throttle setting.
>>>
>>>    SYNOPSIS
>>>      blkiothrottle<domain>    <device>    [--bps<number>] [--bps_rd
>>> <number>] [--bps_wr<number>] [--iops<number>] [--iops_rd<number>]
>>> [--iops_wr<number>]
>>>
>>>    DESCRIPTION
>>>      Set or display a block disk I/O throttle setting.
>>>
>>>    OPTIONS
>>>      [--domain]<string>     domain name, id or uuid
>>>      [--device]<string>     block device
>>>      --bps<number>      total throughput limits in bytes/s
>>>      --bps_rd<number>     read throughput limits in bytes/s
>>>      --bps_wr<number>     write throughput limits in bytes/s
>>>      --iops<number>     total operation limits in numbers/s
>>>      --iops_rd<number>     read operation limits in numbers/s
>>>      --iops_wr<number>     write operation limits in numbers/s
>>>
>> How to display the current I/O throttle setting of a specific block device
>> here?
> It will show as below:
> virtio0: bps=xxx, bps_rd=xxx, bps_wr=xxx, iops=xxx, iops_rd=xxx, iops_wr=xxx.

With which options to the command?  I guess "blkiothrottle <domain> 
<device>" will display the current setting.

  reply	other threads:[~2011-08-30  8:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30  2:55 [Qemu-devel] The design choice for how to enable block I/O throttling function in libvirt Zhi Yong Wu
2011-08-30  7:18 ` [Qemu-devel] [libvirt] " shu ming
2011-08-30  8:10   ` Zhi Yong Wu
2011-08-30  8:31     ` shu ming [this message]
2011-08-30  8:36       ` Zhi Yong Wu
     [not found] ` <CAJSP0QW1CPCokX=F5z7y==vn1S4wH0VtOaQ7oj4kC7f7uQM4MQ@mail.gmail.com>
     [not found]   ` <20110830134636.GB29130@aglitke.rchland.ibm.com>
     [not found]     ` <CAJSP0QUHm=y8XJC_KXRg7ufFZt3K_XDDfQb--sxjC+c0GjO8qg@mail.gmail.com>
2011-09-01  3:55       ` [Qemu-devel] [RFC] block I/O throttling: how to enable " Zhi Yong Wu
2011-09-01  4:21         ` Osier Yang
2011-09-01  4:51           ` Zhi Yong Wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E5C9FF0.5020206@linux.vnet.ibm.com \
    --to=shuming@linux.vnet.ibm.com \
    --cc=guijianfeng@cn.fujitsu.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zwu.kernel@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.