From: Kevin Wolf <kwolf@redhat.com>
To: Christian Brunner <chb@muc.de>,
Laurent Vivier <Laurent@vivier.eu>,
MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Cc: Qemu-devel@nongnu.org
Subject: [Qemu-devel] bdrv_flush for qemu block drivers nbd, rbd and sheepdog
Date: Thu, 21 Oct 2010 16:07:28 +0200 [thread overview]
Message-ID: <4CC04920.8040902@redhat.com> (raw)
Hi all,
I'm currently looking into adding a return value to qemu's bdrv_flush
function and I noticed that your block drivers (nbd, rbd and sheepdog)
don't implement bdrv_flush at all. bdrv_flush is going to return
-ENOTSUP for any block driver not implementing this, effectively
breaking these three drivers for anything but cache=unsafe.
Is there a specific reason why your drivers don't implement this? I
think I remember that one of the drivers always provides
cache=writethough semantics. It would be okay to silently "upgrade" to
cache=writethrough, so in this case I'd just need to add an empty
bdrv_flush implementation.
Otherwise, we really cannot allow any option except cache=unsafe because
that's the semantics provided by the driver.
In any case, I think it would be a good idea to implement a real
bdrv_flush function to allow the write-back cache modes cache=off and
cache=writeback in order to improve performance over writethrough.
Is this possible with your protocols, or can the protocol be changed to
consider this? Any hints on how to proceed?
Kevin
next reply other threads:[~2010-10-21 14:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 14:07 Kevin Wolf [this message]
2010-10-21 15:07 ` [Qemu-devel] bdrv_flush for qemu block drivers nbd, rbd and sheepdog Anthony Liguori
2010-10-21 19:32 ` Laurent Vivier
2010-10-22 8:29 ` Kevin Wolf
2010-10-22 12:58 ` Anthony Liguori
2010-10-22 13:35 ` Kevin Wolf
2010-10-22 13:45 ` Anthony Liguori
2010-10-22 13:57 ` Kevin Wolf
2010-10-22 14:01 ` Anthony Liguori
2010-10-21 18:49 ` Fwd: " Christian Brunner
2010-10-21 18:59 ` Sage Weil
2010-10-22 8:39 ` Kevin Wolf
2010-10-22 8:39 ` Kevin Wolf
2010-10-22 16:22 ` Sage Weil
2010-10-22 16:22 ` Sage Weil
2010-10-25 7:58 ` Kevin Wolf
2010-10-25 7:58 ` Kevin Wolf
2010-10-22 5:43 ` MORITA Kazutaka
2010-10-22 8:47 ` Kevin Wolf
2010-10-25 5:31 ` MORITA Kazutaka
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=4CC04920.8040902@redhat.com \
--to=kwolf@redhat.com \
--cc=Laurent@vivier.eu \
--cc=Qemu-devel@nongnu.org \
--cc=chb@muc.de \
--cc=morita.kazutaka@lab.ntt.co.jp \
/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.