From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] make sure disk writes actually hit disk
Date: Sat, 29 Jul 2006 11:57:31 +0200 [thread overview]
Message-ID: <44CB310B.9060308@bellard.org> (raw)
In-Reply-To: <44CA6B76.7000004@redhat.com>
Hi,
Using O_SYNC for disk image access is not acceptable: QEMU relies on the
host OS to ensure that the data is written correctly. Even the current
'fsync' support is questionnable to say the least !
Please don't mix issues regarding QEMU disk handling and the underlying
hypervisor/host OS block device handling.
Regards,
Fabrice.
Rik van Riel wrote:
> This is the simple approach to making sure that disk writes actually
> hit disk before we tell the guest OS that IO has completed. Thanks
> to DMA_MULTI_THREAD the performance still seems to be adequate.
>
> A fancier solution would be to make the sync/non-sync behaviour of
> the qemu disk backing store tunable from the guest OS, by tuning
> the IDE disk write cache on/off with hdparm, and having hw/ide.c
> call ->fsync functions in the block backends.
>
> I'm willing to code up the fancy solution if people prefer that.
>
>
> ------------------------------------------------------------------------
>
> Make sure disk writes really made it to disk before we report I/O
> completion to the guest domain. The DMA_MULTI_THREAD functionality
> from the qemu-dm IDE emulation should make the performance overhead
> of synchronous writes bearable, or at least comparable to native
> hardware.
>
> Signed-off-by: Rik van Riel <riel@redhat.com>
>
> --- xen-unstable-10712/tools/ioemu/block-bochs.c.osync 2006-07-28 02:15:56.000000000 -0400
> +++ xen-unstable-10712/tools/ioemu/block-bochs.c 2006-07-28 02:21:08.000000000 -0400
> @@ -91,7 +91,7 @@
> int fd, i;
> struct bochs_header bochs;
>
> - fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE);
> + fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE | O_SYNC);
> if (fd < 0) {
> fd = open(filename, O_RDONLY | O_BINARY | O_LARGEFILE);
> if (fd < 0)
> --- xen-unstable-10712/tools/ioemu/block.c.osync 2006-07-28 02:15:56.000000000 -0400
> +++ xen-unstable-10712/tools/ioemu/block.c 2006-07-28 02:19:27.000000000 -0400
> @@ -677,7 +677,7 @@
> int rv;
> #endif
>
> - fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE);
> + fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE | O_SYNC);
> if (fd < 0) {
> fd = open(filename, O_RDONLY | O_BINARY | O_LARGEFILE);
> if (fd < 0)
> --- xen-unstable-10712/tools/ioemu/block-cloop.c.osync 2006-07-28 02:15:56.000000000 -0400
> +++ xen-unstable-10712/tools/ioemu/block-cloop.c 2006-07-28 02:17:13.000000000 -0400
> @@ -55,7 +55,7 @@
> BDRVCloopState *s = bs->opaque;
> uint32_t offsets_size,max_compressed_block_size=1,i;
>
> - s->fd = open(filename, O_RDONLY | O_BINARY | O_LARGEFILE);
> + s->fd = open(filename, O_RDONLY | O_BINARY | O_LARGEFILE | O_SYNC);
> if (s->fd < 0)
> return -1;
> bs->read_only = 1;
> --- xen-unstable-10712/tools/ioemu/block-cow.c.osync 2006-07-28 02:15:56.000000000 -0400
> +++ xen-unstable-10712/tools/ioemu/block-cow.c 2006-07-28 02:21:34.000000000 -0400
> @@ -69,7 +69,7 @@
> struct cow_header_v2 cow_header;
> int64_t size;
>
> - fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE);
> + fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE | O_SYNC);
> if (fd < 0) {
> fd = open(filename, O_RDONLY | O_BINARY | O_LARGEFILE);
> if (fd < 0)
> --- xen-unstable-10712/tools/ioemu/block-qcow.c.osync 2006-07-28 02:15:56.000000000 -0400
> +++ xen-unstable-10712/tools/ioemu/block-qcow.c 2006-07-28 02:20:05.000000000 -0400
> @@ -95,7 +95,7 @@
> int fd, len, i, shift;
> QCowHeader header;
>
> - fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE);
> + fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE | O_SYNC);
> if (fd < 0) {
> fd = open(filename, O_RDONLY | O_BINARY | O_LARGEFILE);
> if (fd < 0)
> --- xen-unstable-10712/tools/ioemu/block-vmdk.c.osync 2006-07-28 02:15:56.000000000 -0400
> +++ xen-unstable-10712/tools/ioemu/block-vmdk.c 2006-07-28 02:20:20.000000000 -0400
> @@ -96,7 +96,7 @@
> uint32_t magic;
> int l1_size;
>
> - fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE);
> + fd = open(filename, O_RDWR | O_BINARY | O_LARGEFILE | O_SYNC);
> if (fd < 0) {
> fd = open(filename, O_RDONLY | O_BINARY | O_LARGEFILE);
> if (fd < 0)
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2006-07-29 9:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 19:54 [Qemu-devel] [RFC][PATCH] make sure disk writes actually hit disk Rik van Riel
2006-07-28 19:58 ` [Qemu-devel] " Rik van Riel
2006-07-28 20:12 ` Anthony Liguori
2006-07-28 20:18 ` Rik van Riel
2006-07-28 20:30 ` Paul Brook
2006-07-28 20:43 ` Rik van Riel
2006-07-28 21:01 ` Paul Brook
2006-07-31 7:08 ` Jens Axboe
2006-07-29 9:57 ` Fabrice Bellard [this message]
2006-07-29 14:59 ` [Qemu-devel] " Rik van Riel
2006-07-29 16:04 ` Paul Brook
2006-07-29 16:22 ` Rik van Riel
2006-07-29 16:31 ` Paul Brook
2006-07-31 7:08 ` Jens Axboe
2006-07-29 17:33 ` Bill C. Riemers
2006-07-30 21:47 ` Jamie Lokier
2006-07-30 21:41 ` Jamie Lokier
2006-07-31 9:52 ` andrzej zaborowski
2006-07-31 10:17 ` Jens Axboe
2006-07-31 17:50 ` andrzej zaborowski
2006-07-31 7:08 ` Jens Axboe
2006-07-31 7:56 ` Jonas Maebe
2006-07-31 8:18 ` Jens Axboe
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=44CB310B.9060308@bellard.org \
--to=fabrice@bellard.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 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.