From: Alex Bligh <alex@alex.org.uk>
To: qemu-devel@nongnu.org
Cc: Alex Bligh <alex@alex.org.uk>
Subject: [Qemu-devel] Adding a persistent writeback cache to qemu
Date: Mon, 01 Apr 2013 13:21:45 +0000 [thread overview]
Message-ID: <7029962A8C6EFDBC98B51E44@nimrod.local> (raw)
I'd like to experiment with adding persistent writeback cache to qemu.
The use case here is where non-local storage is used (e.g. rbd, ceph)
using the qemu drivers, together with a local cache as a file on
a much faster locally mounted device, for instance an SSD (possibly
replicated). This would I think give a similar performance boost to
using an rbd block device plus flashcache/dm-cache/bcache, but without
introducing all the context switches and limitations of having to
use real block devices. I appreciate it would need to be live migration
aware (worst case solution: flush and turn off caching during live
migrate), and ideally be capable of replaying a dirty writeback cache
in the event the host crashes.
Is there any support for this already? Has anyone worked on this before?
If not, would there be any interest in it?
--
Alex Bligh
next reply other threads:[~2013-04-01 12:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 13:21 Alex Bligh [this message]
2013-04-11 9:25 ` [Qemu-devel] Adding a persistent writeback cache to qemu Stefan Hajnoczi
2013-06-19 21:28 ` Alex Bligh
2013-06-20 9:46 ` Stefan Hajnoczi
2013-06-20 14:25 ` Alex Bligh
2013-06-21 12:55 ` Stefan Hajnoczi
2013-06-21 13:54 ` Alex Bligh
2013-06-21 15:45 ` Sage Weil
2013-06-20 15:58 ` Sage Weil
2013-06-21 11:18 ` Alex Bligh
2013-06-21 15:40 ` Sage Weil
2013-06-21 13:20 ` Stefan Hajnoczi
2013-06-21 15:18 ` Liu Yuan
2013-06-24 9:31 ` Stefan Hajnoczi
2013-06-24 10:25 ` Alex Bligh
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=7029962A8C6EFDBC98B51E44@nimrod.local \
--to=alex@alex.org.uk \
--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).