From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:36649) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QyIbZ-0001Tf-HC for qemu-devel@nongnu.org; Tue, 30 Aug 2011 03:19:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QyIbY-0006fv-LI for qemu-devel@nongnu.org; Tue, 30 Aug 2011 03:19:29 -0400 Received: from e23smtp01.au.ibm.com ([202.81.31.143]:34273) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QyIbY-0006ep-2A for qemu-devel@nongnu.org; Tue, 30 Aug 2011 03:19:28 -0400 Received: from d23relay04.au.ibm.com (d23relay04.au.ibm.com [202.81.31.246]) by e23smtp01.au.ibm.com (8.14.4/8.13.1) with ESMTP id p7U7EXXn021537 for ; Tue, 30 Aug 2011 17:14:33 +1000 Received: from d23av03.au.ibm.com (d23av03.au.ibm.com [9.190.234.97]) by d23relay04.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p7U7HoH51421342 for ; Tue, 30 Aug 2011 17:17:50 +1000 Received: from d23av03.au.ibm.com (loopback [127.0.0.1]) by d23av03.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p7U7JD9H001060 for ; Tue, 30 Aug 2011 17:19:13 +1000 Message-ID: <4E5C8EB9.7080308@linux.vnet.ibm.com> Date: Tue, 30 Aug 2011 15:18:17 +0800 From: shu ming MIME-Version: 1.0 References: 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, QEMU Developers 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? I prfer to have less command to be as simple as possible for users. But it seems that we need another command here instead of having a block IO specific command like "iothrottle". Supposely, the next step of I/O throttling will be network device limit. Shoud we have another new command like "niciothrottle"?