From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, hch@lst.de, aurelien@aurel32.net, avi@redhat.com
Subject: [Qemu-devel] [PATCH] Default to cache=writeback
Date: Wed, 26 May 2010 20:13:14 +0200 [thread overview]
Message-ID: <1274897594-4167-1-git-send-email-agraf@suse.de> (raw)
In the previous discussion Anthony brought up the fact that cache=writeback is
safe enough considering data integrity. If so, I don't see a reason not to use
it as default, as it speeds up things a lot.
Keep in mind that most people will want to use cache=none anyways if they want
to bypass the host cache.
To stress my point, I ran the same test I did for cache=unsafe again to compare
cache=write{through,back}.
cache=writeback
real 0m32.549s
user 0m16.069s
sys 0m6.152s
cache=writethrough
real 0m48.055s
user 0m16.677s
sys 0m8.045s
Signed-off-by: Alexander Graf <agraf@suse.de>
---
qemu-options.hx | 19 +++++++++----------
vl.c | 5 ++++-
2 files changed, 13 insertions(+), 11 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index cea9b72..b389f36 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -162,16 +162,15 @@ This option specifies the serial number to assign to the device.
Specify the controller's PCI address (if=virtio only).
@end table
-By default, writethrough caching is used for all block device. This means that
-the host page cache will be used to read and write data but write notification
-will be sent to the guest only when the data has been reported as written by
-the storage subsystem.
-
-Writeback caching will report data writes as completed as soon as the data is
-present in the host page cache. This is safe as long as you trust your host.
-If your host crashes or loses power, then the guest may experience data
-corruption. When using the @option{-snapshot} option, writeback caching is
-used by default.
+By default, writeback caching is used for all block devices. It will report
+data writes as completed as soon as the data is present in the host page
+cache. This is safe as long as you trust your host. If your host crashes
+or loses power, then the guest may experience data corruption. When using
+the @option{-snapshot} option, writeback caching is always used.
+
+Writethrough caching means that the host page cache will be used to read
+and write data but write notification will be sent to the guest only when
+the data has been reported as written by the storage subsystem.
The host page cache can be avoided entirely with @option{cache=none}. This will
attempt to do disk IO directly to the guests memory. QEMU may still perform
diff --git a/vl.c b/vl.c
index bc15dd7..a70e487 100644
--- a/vl.c
+++ b/vl.c
@@ -917,11 +917,14 @@ DriveInfo *drive_init(QemuOpts *opts, void *opaque,
bdrv_flags |= BDRV_O_CACHE_WB;
bdrv_flags |= BDRV_O_NO_FLUSH;
} else if (!strcmp(buf, "writethrough")) {
- /* this is the default */
+ /* no special flag needed */
} else {
fprintf(stderr, "qemu: invalid cache option\n");
return NULL;
}
+ } else {
+ /* default to writeback */
+ bdrv_flags |= BDRV_O_CACHE_WB;
}
#ifdef CONFIG_LINUX_AIO
--
1.6.0.2
next reply other threads:[~2010-05-26 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 18:13 Alexander Graf [this message]
2010-05-26 19:28 ` [Qemu-devel] [PATCH] Default to cache=writeback Stefan Hajnoczi
2010-06-01 11:31 ` Alexander Graf
2010-06-01 12:46 ` Kevin Wolf
2010-06-01 12:48 ` 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=1274897594-4167-1-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--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.