qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Josh Durgin <josh.durgin@inktank.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] rbd: add an asynchronous flush
Date: Thu, 11 Apr 2013 10:48:44 +0200	[thread overview]
Message-ID: <20130411084844.GD2449@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <20130411080232.GB5253@stefanha-thinkpad.redhat.com>

Am 11.04.2013 um 10:02 hat Stefan Hajnoczi geschrieben:
> On Wed, Apr 10, 2013 at 07:03:39AM -0700, Josh Durgin wrote:
> > On 04/02/2013 07:10 AM, Kevin Wolf wrote:
> > >Am 29.03.2013 um 21:03 hat Josh Durgin geschrieben:
> > >>The existing bdrv_co_flush_to_disk implementation uses rbd_flush(),
> > >>which is sychronous and causes the main qemu thread to block until it
> > >>is complete. This results in unresponsiveness and extra latency for
> > >>the guest.
> > >>
> > >>Fix this by using an asynchronous version of flush.  This was added to
> > >>librbd with a special #define to indicate its presence, since it will
> > >>be backported to stable versions. Thus, there is no need to check the
> > >>version of librbd.
> > >
> > >librbd is linked dynamically and the version on the build host isn't
> > >necessarily the same as the version qemu is run with. So shouldn't this
> > >better be a runtime check?
> > 
> > While we discuss runtime loading separately, would you mind taking this
> > patch as-is for now?
> 
> Hi Josh,
> I'm happy with Patch v3 1/2.  Does that work for you?

Only patch 1/2 would add dead code as .bdrv_aio_flush would never be
called. I think we should rather take v1 of the series then, with the
#ifdefs at build time.

Kevin

  reply	other threads:[~2013-04-11  8:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29  7:59 [Qemu-devel] [PATCH] rbd: add an asynchronous flush Josh Durgin
2013-03-29 20:03 ` [Qemu-devel] [PATCH v2] " Josh Durgin
2013-04-02 14:10   ` Kevin Wolf
2013-04-04  8:35     ` [Qemu-devel] [PATCH v3 1/2] " Josh Durgin
2013-04-04  8:35     ` [Qemu-devel] [PATCH 2/2] rbd: disable unsupported librbd functions at runtime Josh Durgin
2013-04-04 10:10       ` Kevin Wolf
2013-04-04 16:50         ` Josh Durgin
2013-04-05  9:31           ` Kevin Wolf
2013-04-10  0:05             ` [Qemu-devel] [PATCH v3 2/2] rbd: link and load librbd dynamically Josh Durgin
2013-04-10  8:09               ` Stefan Hajnoczi
2013-04-10 14:52                 ` [Qemu-devel] runtime Block driver modules (was Re: [PATCH v3 2/2] rbd: link and load librbd dynamically) Josh Durgin
2013-04-10 15:08                 ` [Qemu-devel] [PATCH v3 2/2] rbd: link and load librbd dynamically Anthony Liguori
2013-04-10 21:19                   ` Paolo Bonzini
2013-04-11  8:04                     ` Stefan Hajnoczi
2013-04-11  7:59                   ` Stefan Hajnoczi
2013-06-21 18:42                   ` Sage Weil
2013-06-21 19:08                     ` Alex Bligh
2013-06-21 19:13                     ` Anthony Liguori
2013-04-10 14:03     ` [Qemu-devel] [PATCH v2] rbd: add an asynchronous flush Josh Durgin
2013-04-11  8:02       ` Stefan Hajnoczi
2013-04-11  8:48         ` Kevin Wolf [this message]
2013-04-11 17:19           ` Josh Durgin
2013-04-12  6:50             ` Kevin Wolf
2013-04-12  7:42               ` 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=20130411084844.GD2449@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=josh.durgin@inktank.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).