qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kwolf@redhat.com, stefanha@linux.vnet.ibm.com,
	kvm@vger.kernel.org, guijianfeng@cn.fujitsu.com,
	qemu-devel@nongnu.org, wuzhy@cn.ibm.com,
	herbert@gondor.hengli.com.au,
	Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
	luowenj@cn.ibm.com, zhanx@cn.ibm.com, zhaoyang@cn.ibm.com,
	llim@redhat.com, Ryan A Harper <raharper@us.ibm.com>
Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits
Date: Tue, 31 May 2011 09:25:31 -0500	[thread overview]
Message-ID: <4DE4FA5B.1090804@codemonkey.ws> (raw)
In-Reply-To: <20110531140402.GF16382@redhat.com>

On 05/31/2011 09:04 AM, Vivek Goyal wrote:
> On Tue, May 31, 2011 at 08:50:40AM -0500, Anthony Liguori wrote:
>> On 05/31/2011 08:45 AM, Vivek Goyal wrote:
>>> On Mon, May 30, 2011 at 01:09:23PM +0800, Zhi Yong Wu wrote:
>>>> Hello, all,
>>>>
>>>>      I have prepared to work on a feature called "Disk I/O limits" for qemu-kvm projeect.
>>>>      This feature will enable the user to cap disk I/O amount performed by a VM.It is important for some storage resources to be shared among multi-VMs. As you've known, if some of VMs are doing excessive disk I/O, they will hurt the performance of other VMs.
>>>>
>>>
>>> Hi Zhiyong,
>>>
>>> Why not use kernel blkio controller for this and why reinvent the wheel
>>> and implement the feature again in qemu?
>>
>> blkio controller only works for block devices.  It doesn't work when
>> using files.
>
> So can't we comeup with something to easily determine which device backs
> up this file? Though that will still not work for NFS backed storage
> though.

Right.

Additionally, in QEMU, we can rate limit based on concepts that make 
sense to a guest.  We can limit the actual I/O ops visible to the guest 
which means that we'll get consistent performance regardless of whether 
the backing file is qcow2, raw, LVM, or raw over NFS.

The kernel just doesn't have enough information to do a good job here.

Regards,

Anthony Liguori

>
> Thanks
> Vivek
>

  reply	other threads:[~2011-05-31 14:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30  5:09 [Qemu-devel] [RFC]QEMU disk I/O limits Zhi Yong Wu
2011-05-31 13:45 ` Vivek Goyal
2011-05-31 13:50   ` Anthony Liguori
2011-05-31 14:04     ` Vivek Goyal
2011-05-31 14:25       ` Anthony Liguori [this message]
2011-05-31 17:59         ` Vivek Goyal
2011-05-31 18:39           ` Anthony Liguori
2011-05-31 19:24             ` Vivek Goyal
2011-05-31 23:30               ` Anthony Liguori
2011-06-01 13:20                 ` Vivek Goyal
2011-06-01 21:15                   ` Stefan Hajnoczi
2011-06-01 21:42                     ` Vivek Goyal
2011-06-01 22:28                       ` Stefan Hajnoczi
2011-06-04  8:54                 ` Blue Swirl
2011-05-31 20:48             ` Mike Snitzer
2011-05-31 22:22               ` Anthony Liguori
2011-05-31 13:56   ` Daniel P. Berrange
2011-05-31 14:10     ` Vivek Goyal
2011-05-31 14:19       ` Daniel P. Berrange
2011-05-31 14:28         ` Vivek Goyal
2011-05-31 15:28         ` Ryan Harper
2011-05-31 19:55 ` Vivek Goyal
2011-06-01  3:12   ` Zhi Yong Wu
2011-06-02  9:33     ` Michal Suchanek
2011-06-03  6:56       ` Zhi Yong Wu
2011-06-01  3:19   ` Zhi Yong Wu
2011-06-01 13:32     ` Vivek Goyal
2011-06-02  6:07       ` Zhi Yong Wu
2011-06-02  6:17 ` Sasha Levin
2011-06-02  6:29   ` Zhi Yong Wu
2011-06-02  7:15     ` Sasha Levin
2011-06-02  8:18       ` Zhi Yong Wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DE4FA5B.1090804@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=guijianfeng@cn.fujitsu.com \
    --cc=herbert@gondor.hengli.com.au \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=llim@redhat.com \
    --cc=luowenj@cn.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raharper@us.ibm.com \
    --cc=stefanha@linux.vnet.ibm.com \
    --cc=vgoyal@redhat.com \
    --cc=wuzhy@cn.ibm.com \
    --cc=wuzhy@linux.vnet.ibm.com \
    --cc=zhanx@cn.ibm.com \
    --cc=zhaoyang@cn.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).