Re: [libvirt] [RFC] block I/O throttling: how to enable in libvirt

From: Adam Litke <agl(a)us.ibm.com&gt; To: Zhi Yong Wu <wuzhy(a)linux.vnet.ibm.com&gt; Cc: libvir-list(a)redhat.com Subject: Re: [libvirt] [RFC] block I/O throttling: how to enable in libvirt Message-ID: <20110902133419.GW15683(a)aglitke.rchland.ibm.com&gt; References: <20110901050531.GB17963(a)f15.cn.ibm.com&gt; <20110902021447.GD19143(a)f15.cn.ibm.com&gt; MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110902021447.GD19143(a)f15.cn.ibm.com&gt; User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: AAAAAA== X-Xagent-From: agl(a)us.ibm.com X-Xagent-To: wuzhy(a)linux.vnet.ibm.com X-Xagent-Gateway: vmsdvma.vnet.ibm.com (XAGENTU8 at VMSDVMA) On Fri, Sep 02, 2011 at 10:14:48AM +0800, Zhi Yong Wu wrote: > On Thu, Sep 01, 2011 at 01:05:31PM +0800, Zhi Yong Wu wrote: > HI, Adam, > Now stefan, Daniel, and Gui all suggest extending blkiotune to keep libivrt unified interface. What do you think of it? It seems like it would be nice to extend the blkiotune API for this use case, but there is one problem. The blkiotune interface operates at the VM level and the QEMU throttling is at the disk level. So if you want per-disk throttling granularity the blkiotune API may not be suitable. I see 3 possible paths forward: 1) Accept the blkiotune limitation of a global setting and add a throttle option that assigns the same throttle value to all disks. <blkiotune> <shares>250</shares> <throttle>1024</throttle> </blkiotune> + Nice for simplicity and ease of implementation - May be too simplistic (can't set different throttling for different disks) 2) Extend the blkiotune API to allow per-disk tunings: <blkiotune> <shares>250</shares> <throttle device='virtio-disk0'>1024</throttle> </blkiotune> + Use an existing API - Unfortunately it doesn't look like this can be done cleanly 3) Use a new API virDomainSetBlkDevParameters() to set device specific tuning parameters: <blkiotune> <shares>250</shares> </blkiotune> ... <disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='...'/> <target dev='vda' bus='virtio'/> <blkdevtune> <throttle>1024</throttle>

</blkdevtune> </disk> + Throttle can be specified with the disk it is effecting - Proliferation of tuning APIs Obviously #1 is the best if you can accept the limitations of the API. #2 would

be nice if we could figure out how to extend virTypedParameter to represent a

(disk, param) pair. I see #3 as a last resort. Did I miss any other solutions.

Did I just manage to completely over-complicate this? :)

-- Adam Litke <agl(a)us.ibm.com&gt; IBM Linux Technology Center