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:12:55 +0800 Message-ID: <20110601031255.GG18832@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: vgoyal@redhat.com, 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 To: Vivek Goyal Return-path: Received: from e28smtp02.in.ibm.com ([122.248.162.2]:35888 "EHLO e28smtp02.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933108Ab1FADOZ (ORCPT ); Tue, 31 May 2011 23:14:25 -0400 Received: from d28relay03.in.ibm.com (d28relay03.in.ibm.com [9.184.220.60]) by e28smtp02.in.ibm.com (8.14.4/8.13.1) with ESMTP id p513ENvI002643 for ; Wed, 1 Jun 2011 08:44:23 +0530 Received: from d28av01.in.ibm.com (d28av01.in.ibm.com [9.184.220.63]) by d28relay03.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p513EMY84517890 for ; Wed, 1 Jun 2011 08:44:22 +0530 Received: from d28av01.in.ibm.com (loopback [127.0.0.1]) by d28av01.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p513EL1O024383 for ; Wed, 1 Jun 2011 08:44:22 +0530 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? 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41104) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRbt9-0004Pg-IJ for qemu-devel@nongnu.org; Tue, 31 May 2011 23:14:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QRbt7-0004sD-P7 for qemu-devel@nongnu.org; Tue, 31 May 2011 23:14:31 -0400 Received: from e28smtp08.in.ibm.com ([122.248.162.8]:50158) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRbt6-0004s3-RS for qemu-devel@nongnu.org; Tue, 31 May 2011 23:14:29 -0400 Received: from d28relay05.in.ibm.com (d28relay05.in.ibm.com [9.184.220.62]) by e28smtp08.in.ibm.com (8.14.4/8.13.1) with ESMTP id p51365LI025270 for ; Wed, 1 Jun 2011 08:36:05 +0530 Received: from d28av01.in.ibm.com (d28av01.in.ibm.com [9.184.220.63]) by d28relay05.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p513EMtv3248216 for ; Wed, 1 Jun 2011 08:44:23 +0530 Received: from d28av01.in.ibm.com (loopback [127.0.0.1]) by d28av01.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p513EL1I024383 for ; Wed, 1 Jun 2011 08:44:22 +0530 Date: Wed, 1 Jun 2011 11:12:55 +0800 From: Zhi Yong Wu Message-ID: <20110601031255.GG18832@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? 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 >