From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Fam Zheng <famz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Eric Blake <eblake@redhat.com>,
qemu-block@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Max Reitz <mreitz@redhat.com>, Sergio Lopez <slp@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/2] block/file-posix: allow -drive cache.direct=off live migration
Date: Fri, 27 Apr 2018 17:23:10 +0100 [thread overview]
Message-ID: <20180427162312.18583-1-stefanha@redhat.com> (raw)
v2:
* Add comment on !__linux__ situation [Fam]
* Add file-posix.c x-check-cache-dropped=on|off option [DaveG, Kevin]
file-posix.c only supports shared storage live migration with -drive
cache.direct=off due to cache consistency issues. There are two main shared
storage configurations: files on NFS and host block devices on SAN LUNs.
The problem is that QEMU starts on the destination host before the source host
has written everything out to the disk. The page cache on the destination host
may contain stale data read when QEMU opened the image file (before migration
handover). Using O_DIRECT avoids this problem but prevents users from taking
advantage of the host page cache.
Although cache=none is the recommended setting for virtualization use cases,
there are scenarios where cache=writeback makes sense. If the guest has much
less RAM than the host or many guests share the same backing file, then the
host page cache can significantly improve disk I/O performance.
This patch series implements .bdrv_co_invalidate_cache() for block/file-posix.c
on Linux so that shared storage live migration works. I have sent it as an RFC
because cache consistency is not binary, there are corner cases which I've
described in the actual patch, and this may require more discussion.
Regarding NFS, QEMU relies on O_DIRECT rather than the close-to-open
consistency model (see nfs(5)), which is the basic guarantee provided by NFS.
After this patch cache consistency is no longer provided by O_DIRECT.
This patch series relies on fdatasync(2) (source) +
posix_fadvise(POSIX_FADV_DONTNEED) (destination) instead. I believe it is safe
for both NFS and SAN LUNs. Maybe we should use fsync(2) instead of
fdatasync(2) so that NFS has up-to-date inode metadata?
Stefan Hajnoczi (2):
block/file-posix: implement bdrv_co_invalidate_cache() on Linux
block/file-posix: add x-check-page-cache=on|off option
qapi/block-core.json | 7 ++-
block/file-posix.c | 146 ++++++++++++++++++++++++++++++++++++++++++++++++++-
2 files changed, 150 insertions(+), 3 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-27 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 16:23 Stefan Hajnoczi [this message]
2018-04-27 16:23 ` [Qemu-devel] [PATCH v2 1/2] block/file-posix: implement bdrv_co_invalidate_cache() on Linux Stefan Hajnoczi
2018-04-27 16:23 ` [Qemu-devel] [PATCH v2 2/2] block/file-posix: add x-check-page-cache=on|off option Stefan Hajnoczi
2018-05-03 7:33 ` [Qemu-devel] [PATCH v2 0/2] block/file-posix: allow -drive cache.direct=off live migration Fam Zheng
2018-05-08 10:32 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2018-05-08 10:46 ` Kevin Wolf
2018-05-11 15:50 ` [Qemu-devel] " Stefan Hajnoczi
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=20180427162312.18583-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=slp@redhat.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).