From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42435) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmOE0-0008DI-Q7 for qemu-devel@nongnu.org; Thu, 28 Jul 2011 06:53:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QmODz-0003Z5-74 for qemu-devel@nongnu.org; Thu, 28 Jul 2011 06:53:56 -0400 Received: from e32.co.us.ibm.com ([32.97.110.150]:44701) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmODy-0003Ys-Pe for qemu-devel@nongnu.org; Thu, 28 Jul 2011 06:53:55 -0400 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e32.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p6S9hvFQ008890 for ; Thu, 28 Jul 2011 03:43:57 -0600 Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p6SAqb8M096842 for ; Thu, 28 Jul 2011 04:52:37 -0600 Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p6S4qa8S028159 for ; Wed, 27 Jul 2011 22:52:36 -0600 From: Zhi Yong Wu Date: Thu, 28 Jul 2011 18:49:24 +0800 Message-Id: <1311850166-9404-1-git-send-email-wuzhy@linux.vnet.ibm.com> Subject: [Qemu-devel] [PATCH v3 0/2] The intro for QEMU disk I/O limits List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kwolf@redhat.com, aliguori@us.ibm.com, stefanha@linux.vnet.ibm.com, kvm@vger.kernel.org, mtosatti@redhat.com, Zhi Yong Wu , zwu.kernel@gmail.com, ryanh@us.ibm.com, luowenj@cn.ibm.com The main goal of the patch is to effectively cap the disk I/O speed or counts of one single VM.It is only one draft, so it unavoidably has some drawbacks, if you catch them, please let me know. The patch will mainly introduce one block I/O throttling algorithm, one timer and one block queue for each I/O limits enabled drive. When a block request is coming in, the throttling algorithm will check if its I/O rate or counts exceed the limits; if yes, then it will enqueue to the block queue; The timer will periodically handle the I/O requests in it. Some available features follow as below: (1) global bps limit. -drive bps=xxx in bytes/s (2) only read bps limit -drive bps_rd=xxx in bytes/s (3) only write bps limit -drive bps_wr=xxx in bytes/s (4) global iops limit -drive iops=xxx in ios/s (5) only read iops limit -drive iops_rd=xxx in ios/s (6) only write iops limit -drive iops_wr=xxx in ios/s (7) the combination of some limits. -drive bps=xxx,iops=xxx Known Limitations: (1) #1 can not coexist with #2, #3 (2) #4 can not coexist with #5, #6 (3) When bps/iops limits are specified to a small value such as 511 bytes/s, this VM will hang up. We are considering how to handle this senario. Zhi Yong Wu (2): v3: Added the code for extending slice time, and modified the method to compute wait time for the timer. The command line support for QEMU disk I/O limits The implement of block queue, block timer, and I/O throttling algorithm v2: The codes V2 for QEMU disk I/O limits. Modified the codes mainly based on stefan's comments. v1: Submit the codes for QEMU disk I/O limits. Only a code draft. Makefile.objs | 2 +- block.c | 302 +++++++++++++++++++++++++++++++++++++++++++++++++++++-- block.h | 1 - block_int.h | 29 ++++++ blockdev.c | 22 ++++ qemu-config.c | 24 +++++ qemu-option.c | 17 +++ qemu-option.h | 1 + qemu-options.hx | 1 + 9 files changed, 389 insertions(+), 10 deletions(-) -- 1.7.2.3