From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kwolf@redhat.com, stefanha@linux.vnet.ibm.com,
Mike Snitzer <snitzer@redhat.com>,
guijianfeng@cn.fujitsu.com, qemu-devel@nongnu.org,
wuzhy@cn.ibm.com, herbert@gondor.hengli.com.au,
Joe Thornber <ejt@redhat.com>,
Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
luowenj@cn.ibm.com, kvm@vger.kernel.org, zhanx@cn.ibm.com,
zhaoyang@cn.ibm.com, llim@redhat.com,
Ryan A Harper <raharper@us.ibm.com>
Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits
Date: Thu, 2 Jun 2011 14:07:45 +0800 [thread overview]
Message-ID: <20110602060745.GK18832@f12.cn.ibm.com> (raw)
In-Reply-To: <20110601133232.GC21638@redhat.com>
On Wed, Jun 01, 2011 at 09:32:32AM -0400, Vivek Goyal wrote:
>Date: Wed, 1 Jun 2011 09:32:32 -0400
>From: Vivek Goyal <vgoyal@redhat.com>
>To: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>Cc: kwolf@redhat.com, stefanha@linux.vnet.ibm.com, kvm@vger.kernel.org,
> guijianfeng@cn.fujitsu.com, qemu-devel@nongnu.org, wuzhy@cn.ibm.com,
> herbert@gondor.hengli.com.au, ejt@redhat.com, luowenj@cn.ibm.com,
> zhanx@cn.ibm.com, zhaoyang@cn.ibm.com, llim@redhat.com,
> raharper@us.ibm.com
>Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits
>User-Agent: Mutt/1.5.21 (2010-09-15)
>
>On Wed, Jun 01, 2011 at 11:19:58AM +0800, Zhi Yong Wu wrote:
>> On Tue, May 31, 2011 at 03:55:49PM -0400, Vivek Goyal wrote:
>> >Date: Tue, 31 May 2011 15:55:49 -0400
>> >From: Vivek Goyal <vgoyal@redhat.com>
>> >To: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>> >Cc: kwolf@redhat.com, aliguori@us.ibm.com, stefanha@linux.vnet.ibm.com,
>> > kvm@vger.kernel.org, guijianfeng@cn.fujitsu.com,
>> > qemu-devel@nongnu.org, wuzhy@cn.ibm.com,
>> > herbert@gondor.hengli.com.au, luowenj@cn.ibm.com, zhanx@cn.ibm.com,
>> > zhaoyang@cn.ibm.com, llim@redhat.com, raharper@us.ibm.com
>> >Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits
>> >User-Agent: Mutt/1.5.21 (2010-09-15)
>> >
>> >On Mon, May 30, 2011 at 01:09:23PM +0800, Zhi Yong Wu wrote:
>> >
>> >[..]
>> >> 3.) How the users enable and play with it
>> >> QEMU -drive option will be extended so that disk I/O limits can be specified on its command line, such as -drive [iops=xxx,][throughput=xxx] or -drive [iops_rd=xxx,][iops_wr=xxx,][throughput=xxx] etc. When this argument is specified, it means that "disk I/O limits" feature is enabled for this drive disk.
>> >
>> >How does throughput interface look like? is it bytes per second or something
>> >else?
>> Given your suggestion, its form will look like below:
>>
>> -drive [iops=xxx][,bps=xxx] or -drive [iops_rd=xxx][,iops_wr=xxx][,bps_rd=xxx][,bps_wr=xxx]
>
>Can one specify both iops and bps rule for the same drive?
Right. They both will together limit runtime I/O rate.
Regards,
Zhiyong Wu
>
>Thanks
>Vivek
next prev parent reply other threads:[~2011-06-02 6:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 5:09 [Qemu-devel] [RFC]QEMU disk I/O limits Zhi Yong Wu
2011-05-31 13:45 ` Vivek Goyal
2011-05-31 13:50 ` Anthony Liguori
2011-05-31 14:04 ` Vivek Goyal
2011-05-31 14:25 ` Anthony Liguori
2011-05-31 17:59 ` Vivek Goyal
2011-05-31 18:39 ` Anthony Liguori
2011-05-31 19:24 ` Vivek Goyal
2011-05-31 23:30 ` Anthony Liguori
2011-06-01 13:20 ` Vivek Goyal
2011-06-01 21:15 ` Stefan Hajnoczi
2011-06-01 21:42 ` Vivek Goyal
2011-06-01 22:28 ` Stefan Hajnoczi
2011-06-04 8:54 ` Blue Swirl
2011-05-31 20:48 ` Mike Snitzer
2011-05-31 22:22 ` Anthony Liguori
2011-05-31 13:56 ` Daniel P. Berrange
2011-05-31 14:10 ` Vivek Goyal
2011-05-31 14:19 ` Daniel P. Berrange
2011-05-31 14:28 ` Vivek Goyal
2011-05-31 15:28 ` Ryan Harper
2011-05-31 19:55 ` Vivek Goyal
2011-06-01 3:12 ` Zhi Yong Wu
2011-06-02 9:33 ` Michal Suchanek
2011-06-03 6:56 ` Zhi Yong Wu
2011-06-01 3:19 ` Zhi Yong Wu
2011-06-01 13:32 ` Vivek Goyal
2011-06-02 6:07 ` Zhi Yong Wu [this message]
2011-06-02 6:17 ` Sasha Levin
2011-06-02 6:29 ` Zhi Yong Wu
2011-06-02 7:15 ` Sasha Levin
2011-06-02 8:18 ` 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=20110602060745.GK18832@f12.cn.ibm.com \
--to=wuzhy@linux.vnet.ibm.com \
--cc=ejt@redhat.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=herbert@gondor.hengli.com.au \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=llim@redhat.com \
--cc=luowenj@cn.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=raharper@us.ibm.com \
--cc=snitzer@redhat.com \
--cc=stefanha@linux.vnet.ibm.com \
--cc=vgoyal@redhat.com \
--cc=wuzhy@cn.ibm.com \
--cc=zhanx@cn.ibm.com \
--cc=zhaoyang@cn.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).