From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:37076) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRPRY-0008Ih-Rh for qemu-devel@nongnu.org; Tue, 31 May 2011 09:57:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QRPRQ-0005Oo-BU for qemu-devel@nongnu.org; Tue, 31 May 2011 09:57:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:18472) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QRPRQ-0005OM-4W for qemu-devel@nongnu.org; Tue, 31 May 2011 09:57:04 -0400 Date: Tue, 31 May 2011 14:56:46 +0100 From: "Daniel P. Berrange" Message-ID: <20110531135646.GF17656@redhat.com> References: <20110530050923.GF18832@f12.cn.ibm.com> <20110531134537.GE16382@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20110531134537.GE16382@redhat.com> Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits Reply-To: "Daniel P. Berrange" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vivek Goyal 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, Zhi Yong Wu , 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 09:45:37AM -0400, Vivek Goyal wrote: > On Mon, May 30, 2011 at 01:09:23PM +0800, Zhi Yong Wu wrote: > > Hello, all, > > > > I have prepared to work on a feature called "Disk I/O limits" for qemu-kvm projeect. > > This feature will enable the user to cap disk I/O amount performed by a VM.It is important for some storage resources to be shared among multi-VMs. As you've known, if some of VMs are doing excessive disk I/O, they will hurt the performance of other VMs. > > > > Hi Zhiyong, > > Why not use kernel blkio controller for this and why reinvent the wheel > and implement the feature again in qemu? The finest level of granularity offered by cgroups apply limits per QEMU process. So the blkio controller can't be used to apply controls directly to individual disks used by QEMU, only the VM as a whole. We networking we can use 'net_cls' cgroups controller for the process as a whole, or attach 'tc' to individual TAP devices for per-NIC throttling, both of which ultimately use the same kernel functionality. I don't see an equivalent option for throttling individual disks that would reuse functionality from the blkio controller. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|