From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:52344)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vgoyal@redhat.com>) id 1QRlXW-0001Cu-EU
	for qemu-devel@nongnu.org; Wed, 01 Jun 2011 09:32:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vgoyal@redhat.com>) id 1QRlXQ-0008EW-Ux
	for qemu-devel@nongnu.org; Wed, 01 Jun 2011 09:32:49 -0400
Received: from mx1.redhat.com ([209.132.183.28]:60110)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vgoyal@redhat.com>) id 1QRlXQ-0008EE-GQ
	for qemu-devel@nongnu.org; Wed, 01 Jun 2011 09:32:44 -0400
Date: Wed, 1 Jun 2011 09:32:32 -0400
From: Vivek Goyal <vgoyal@redhat.com>
Message-ID: <20110601133232.GC21638@redhat.com>
References: <20110530050923.GF18832@f12.cn.ibm.com>
	<20110531195549.GL16382@redhat.com>
	<20110601031958.GH18832@f12.cn.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110601031958.GH18832@f12.cn.ibm.com>
Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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

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?

Thanks
Vivek