[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC]QEMU disk I/O limits
From: |
Zhi Yong Wu |
Subject: |
Re: [Qemu-devel] [RFC]QEMU disk I/O limits |
Date: |
Wed, 1 Jun 2011 11:12:55 +0800 |
User-agent: |
Mutt/1.5.20 (2009-08-17) |
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 <address@hidden>
>To: Zhi Yong Wu <address@hidden>
>Cc: address@hidden, address@hidden, address@hidden,
> address@hidden, address@hidden,
> address@hidden, address@hidden,
> address@hidden, address@hidden, address@hidden,
> address@hidden, address@hidden, address@hidden
>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?
HI, Vivek,
It will be a value based on bytes per second.
>
>Do we have read and write variants for throughput as we have for iops.
QEMU code has two variants "rd_bytes, wr_bytes", but we maybe need to get their
bytes per second.
>
>if you have bytes interface(as kenrel does), then "bps_rd" and "bps_wr"
>might be good names too for thoughput interface.
I agree with you, and can change them as your suggestions.
Regards,
Zhiyong Wu
>
>Thanks
>Vivek
>
Re: [Qemu-devel] [RFC]QEMU disk I/O limits, Daniel P. Berrange, 2011/05/31
Re: [Qemu-devel] [RFC]QEMU disk I/O limits, Vivek Goyal, 2011/05/31