From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhi Yong Wu Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits Date: Wed, 1 Jun 2011 11:19:58 +0800 Message-ID: <20110601031958.GH18832@f12.cn.ibm.com> References: <20110530050923.GF18832@f12.cn.ibm.com> <20110531195549.GL16382@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, wuzhy@linux.vnet.ibm.com, luowenj@cn.ibm.com, zhanx@cn.ibm.com, zhaoyang@cn.ibm.com, llim@redhat.com, raharper@us.ibm.com, vgoyal@redhat.com To: Vivek Goyal Return-path: Received: from e23smtp02.au.ibm.com ([202.81.31.144]:49024 "EHLO e23smtp02.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933153Ab1FADV3 (ORCPT ); Tue, 31 May 2011 23:21:29 -0400 Received: from d23relay03.au.ibm.com (d23relay03.au.ibm.com [202.81.31.245]) by e23smtp02.au.ibm.com (8.14.4/8.13.1) with ESMTP id p513FbtD015050 for ; Wed, 1 Jun 2011 13:15:37 +1000 Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.235.139]) by d23relay03.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p513LRVl790658 for ; Wed, 1 Jun 2011 13:21:27 +1000 Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) by d23av04.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p513LQF8017073 for ; Wed, 1 Jun 2011 13:21:27 +1000 Content-Disposition: inline In-Reply-To: <20110531195549.GL16382@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 >To: Zhi Yong Wu >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] Regards, Zhiyong Wu > >Do we have read and write variants for throughput as we have for iops. > >if you have bytes interface(as kenrel does), then "bps_rd" and "bps_wr" >might be good names too for thoughput interface. > >Thanks >Vivek > From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:40819) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRc03-0005PW-OO for qemu-devel@nongnu.org; Tue, 31 May 2011 23:21:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QRc02-0005q2-78 for qemu-devel@nongnu.org; Tue, 31 May 2011 23:21:39 -0400 Received: from e23smtp01.au.ibm.com ([202.81.31.143]:49740) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRc01-0005pp-Gi for qemu-devel@nongnu.org; Tue, 31 May 2011 23:21:38 -0400 Received: from d23relay04.au.ibm.com (d23relay04.au.ibm.com [202.81.31.246]) by e23smtp01.au.ibm.com (8.14.4/8.13.1) with ESMTP id p513HF9M029456 for ; Wed, 1 Jun 2011 13:17:15 +1000 Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.235.139]) by d23relay04.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p513KsfN868382 for ; Wed, 1 Jun 2011 13:20:54 +1000 Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) by d23av04.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p513LQF2017073 for ; Wed, 1 Jun 2011 13:21:26 +1000 Date: Wed, 1 Jun 2011 11:19:58 +0800 From: Zhi Yong Wu Message-ID: <20110601031958.GH18832@f12.cn.ibm.com> References: <20110530050923.GF18832@f12.cn.ibm.com> <20110531195549.GL16382@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110531195549.GL16382@redhat.com> Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vivek Goyal 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, wuzhy@linux.vnet.ibm.com, luowenj@cn.ibm.com, zhanx@cn.ibm.com, zhaoyang@cn.ibm.com, llim@redhat.com, raharper@us.ibm.com 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 >To: Zhi Yong Wu >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] Regards, Zhiyong Wu > >Do we have read and write variants for throughput as we have for iops. > >if you have bytes interface(as kenrel does), then "bps_rd" and "bps_wr" >might be good names too for thoughput interface. > >Thanks >Vivek >