qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Adding a persistent writeback cache to qemu
Date: Thu, 11 Apr 2013 11:25:48 +0200	[thread overview]
Message-ID: <20130411092548.GE8904@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <7029962A8C6EFDBC98B51E44@nimrod.local>

On Mon, Apr 01, 2013 at 01:21:45PM +0000, Alex Bligh wrote:
> 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?

I'm concerned about the complexity this would introduce in QEMU.
Therefore I'm a fan of using existing solutions like the Linux block
layer instead of reimplementing this stuff in Linux.

What concrete issues are there with using rbd plus
flashcache/dm-cache/bcache?

I'm not sure I understand the context switch problem since implementing
it in user space will still require system calls to do all the actual
cache I/O.

Stefan

  reply	other threads:[~2013-04-11  9:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 13:21 [Qemu-devel] Adding a persistent writeback cache to qemu Alex Bligh
2013-04-11  9:25 ` Stefan Hajnoczi [this message]
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=20130411092548.GE8904@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=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).