From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:47664) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QyJli-00081t-4m for qemu-devel@nongnu.org; Tue, 30 Aug 2011 04:34:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QyJlh-000452-2b for qemu-devel@nongnu.org; Tue, 30 Aug 2011 04:34:02 -0400 Received: from e28smtp02.in.ibm.com ([122.248.162.2]:38970) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QyJlg-00044r-GL for qemu-devel@nongnu.org; Tue, 30 Aug 2011 04:34:01 -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 p7U8XtM6028513 for ; Tue, 30 Aug 2011 14:03:55 +0530 Received: from d28av05.in.ibm.com (d28av05.in.ibm.com [9.184.220.67]) by d28relay03.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7U8Wdar2318534 for ; Tue, 30 Aug 2011 14:02:39 +0530 Received: from d28av05.in.ibm.com (loopback [127.0.0.1]) by d28av05.in.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7U8Wc1i024822 for ; Tue, 30 Aug 2011 18:32:39 +1000 Message-ID: <4E5C9FF0.5020206@linux.vnet.ibm.com> Date: Tue, 30 Aug 2011 16:31:44 +0800 From: shu ming MIME-Version: 1.0 References: <4E5C8EB9.7080308@linux.vnet.ibm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [libvirt] The design choice for how to enable block I/O throttling function in libvirt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Zhi Yong Wu Cc: libvir-list@redhat.com, guijianfeng@cn.fujitsu.com, QEMU Developers , hutao@cn.fujitsu.com Zhi Yong Wu: > On Tue, Aug 30, 2011 at 3:18 PM, shu ming wrote: >> See commens below. >> Zhi Yong Wu: >>> HI, folks, >>> >>> I am trying to enable block I/O throttling function in libvirt. But >>> currently i met some design questions, and don't make sure if we >>> should extend blkiotune to support block I/O throttling or introduce >>> one new libvirt command "blkiothrottle" to cover it or not. If you >>> have some better idea, pls don't hesitate to drop your comments. >>> >>> If one new libvirt command "blkiothrottle" is introduced, I plan to >>> design its usage syntax as below: >>> >>> virsh # help blkiothrottle >>> NAME >>> blkiothrottle - Set or display a block disk I/O throttle setting. >>> >>> SYNOPSIS >>> blkiothrottle [--bps] [--bps_rd >>> ] [--bps_wr] [--iops] [--iops_rd] >>> [--iops_wr] >>> >>> DESCRIPTION >>> Set or display a block disk I/O throttle setting. >>> >>> OPTIONS >>> [--domain] domain name, id or uuid >>> [--device] block device >>> --bps total throughput limits in bytes/s >>> --bps_rd read throughput limits in bytes/s >>> --bps_wr write throughput limits in bytes/s >>> --iops total operation limits in numbers/s >>> --iops_rd read operation limits in numbers/s >>> --iops_wr write operation limits in numbers/s >>> >> How to display the current I/O throttle setting of a specific block device >> here? > It will show as below: > virtio0: bps=xxx, bps_rd=xxx, bps_wr=xxx, iops=xxx, iops_rd=xxx, iops_wr=xxx. With which options to the command? I guess "blkiothrottle " will display the current setting.