From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: Live migration broken when under heavy IO
Date: Tue, 16 Jun 2009 15:54:12 +0300 [thread overview]
Message-ID: <4A3795F4.9080507@redhat.com> (raw)
In-Reply-To: <4A379504.4080100@us.ibm.com>
On 06/16/2009 03:50 PM, Anthony Liguori wrote:
> Avi Kivity wrote:
>>> Does anyone have a clever idea how to fix this without just waiting
>>> for all IO requests to complete?
>>
>> What's wrong with waiting for requests to complete? It should take a
>> few tens of milliseconds.
>
> An alternative would be to attempt to cancel the requests. This
> incurs no non-deterministic latency.
Yes, that's even better (though without linux-aio, it's equivalent).
>
> The tricky bit is that this has to happen at the device layer because
> the opaques cannot be saved in a meaningful way.
>
Do you mean the device has to record all cancelled requests and replay
them? I think we can do it at the block layer (though we have to avoid
it for nested requests).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-16 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 20:33 [Qemu-devel] Live migration broken when under heavy IO Anthony Liguori
2009-06-15 20:48 ` Glauber Costa
2009-06-16 9:10 ` [Qemu-devel] " Avi Kivity
2009-06-16 9:13 ` Avi Kivity
2009-06-16 12:50 ` Anthony Liguori
2009-06-16 12:54 ` Avi Kivity [this message]
2009-06-16 12:57 ` Anthony Liguori
2009-06-16 13:12 ` Avi Kivity
2009-06-16 18:19 ` Charles Duffy
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=4A3795F4.9080507@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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).