From: Anthony Liguori <anthony@codemonkey.ws>
To: Mike Snitzer <snitzer@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, Joe Thornber <ejt@redhat.com>,
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>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [Qemu-devel] [RFC]QEMU disk I/O limits
Date: Tue, 31 May 2011 17:22:13 -0500 [thread overview]
Message-ID: <4DE56A15.3030804@codemonkey.ws> (raw)
In-Reply-To: <20110531204842.GA16832@redhat.com>
On 05/31/2011 03:48 PM, Mike Snitzer wrote:
> On Tue, May 31 2011 at 2:39pm -0400,
> Anthony Liguori<anthony@codemonkey.ws> wrote:
>
>>> Are you referring to merging taking place which can change the definition
>>> of IOPS as seen by guest?
>>
>> No, with qcow2, it may take multiple real IOPs for what the guest
>> sees as an IOP.
>>
>> That's really the main argument I'm making here. The only entity
>> that knows what a guest IOP corresponds to is QEMU. On the backend,
>> it may end up being a network request, multiple BIOs to physical
>> disks, file access, etc.
>
> Couldn't QEMU give a hint to the kernel about the ratio of guest IOP to
> real IOPs? Or is QEMU blind to the real IOPs that correspond to a guest
> IOP?
Perhaps, but how does that work when the disk image is backed by NFS?
And even if you had a VFS level API, we can do things like libcurl based
block devices in QEMU. So unless you tried to do level 5 traffic
throttling which hopefully, you'll agree is total overkill, we're going
to need to have this functionality in QEMU no matter what.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-05-31 22:22 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
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 [this message]
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=4DE56A15.3030804@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=ejt@redhat.com \
--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=snitzer@redhat.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).