From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:47512) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RKSsR-0006YU-J2 for qemu-devel@nongnu.org; Sun, 30 Oct 2011 06:44:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RKSsQ-0004N7-0R for qemu-devel@nongnu.org; Sun, 30 Oct 2011 06:44:31 -0400 Received: from alpha.arachsys.com ([91.203.57.7]:59673) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RKSsP-0004Mf-RW for qemu-devel@nongnu.org; Sun, 30 Oct 2011 06:44:29 -0400 Date: Sun, 30 Oct 2011 10:44:22 +0000 From: Richard Davies Message-ID: <20111030104422.GD32746@alpha.arachsys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1319796143-9061-1-git-send-email-wuzhy@linux.vnet.ibm.com> Subject: Re: [Qemu-devel] [PATCH v9 0/4] The intro of QEMU block I/O throttling List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Zhi Yong Wu , kwolf@redhat.com Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com Hi, I've been following the evolution of this patch with great interest for use in our qemu-kvm based IaaS public cloud. I am not a qemu developer, but have watched this patch go through many rounds of review and we are very much hoping that it makes it into QEMU 1.0. In a multi-customer multi-VM public cloud environment, disk i/o limiting is absolutely key, and qemu itself is a much better place to do it than with a mix of cgroups and other technologies for each different storage backend. I understand that it is also more efficient: http://www.linux-kvm.org/wiki/images/7/72/2011-forum-keep-a-limit-on-it-io-throttling-in-qemu.pdf As I say, I am not a qemu developer, so cannot practically help, but wanted to post to emphasize the importance of this technology as a consumer of qemu. Best regards, Richard.