From: Kevin Wolf <kwolf@redhat.com>
To: Mark Wu <wudxw@linux.vnet.ibm.com>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] Storage requirements for live migration
Date: Fri, 11 Nov 2011 10:15:10 +0100 [thread overview]
Message-ID: <4EBCE79E.6000209@redhat.com> (raw)
In-Reply-To: <4EBCC051.1060705@linux.vnet.ibm.com>
Am 11.11.2011 07:27, schrieb Mark Wu:
> On 11/11/2011 08:11 AM, Anthony Liguori wrote:
>> I did a brain dump of my understanding of the various storage
>> requirements for live migration. I think it's accurate but I may have
>> misunderstand some details so I would appreciate review.
>>
>> I think given sections (1) and (2), the only viable thing is to
>> require cache=none unless we get new interfaces to flush caches.
> I have two questions:
> 1. why is "cache=writethrough" not reliable? "O_DSYNC" can guarantee
> data is written on disk before the operation is ultimately completed.
> Even if there's synchronization from memory to disk still on-going when
> migration happens, we needn't care about the dirty pages in host memory
> either because the queued request will be re-executed on destination
> host. So I think it's reliable too. Do I miss anything?
The problem is about reading. The destination host reads some pieces of
information during its initialisation, which may later be changed on the
host. After the migration has completed, the destination must not use
the old data that it read previously and that might be in its cache, but
it must access the storage. O_DSYNC doesn't help with that, as reading
still uses the cache there.
Kevin
next prev parent reply other threads:[~2011-11-11 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 0:11 [Qemu-devel] Storage requirements for live migration Anthony Liguori
2011-11-11 6:27 ` Mark Wu
2011-11-11 9:15 ` Kevin Wolf [this message]
2011-11-11 9:38 ` Kevin Wolf
2011-11-11 9:55 ` Daniel P. Berrange
2011-11-11 10:01 ` Kevin Wolf
2011-11-11 14:08 ` Anthony Liguori
2011-11-11 14:05 ` Anthony Liguori
2011-11-11 22:43 ` Ryan Harper
2011-11-11 23:23 ` Anthony Liguori
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=4EBCE79E.6000209@redhat.com \
--to=kwolf@redhat.com \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@linux.vnet.ibm.com \
--cc=wudxw@linux.vnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.