qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	jcody@redhat.com, qemu-devel@nongnu.org,
	"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] blockdev: no need to drain in qmp_block_commit
Date: Thu, 28 May 2015 21:44:41 -0400 (EDT)	[thread overview]
Message-ID: <407042981.6042811.1432863881730.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1432822903-25821-1-git-send-email-pbonzini@redhat.com>



----- Original Message -----
> Draining is not necessary, I/O can happen as soon as the
> commit coroutine yields.  Draining can be necessary before
> reopening the file for read/write, or while modifying the
> backing file chain, but that is done separately in
> bdrv_reopen_multiple or bdrv_close; this particular
> bdrv_drain_all does nothing for that.
> 
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>  blockdev.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/blockdev.c b/blockdev.c
> index d506a70..aee0395 100644
> --- a/blockdev.c
> +++ b/blockdev.c
> @@ -2355,9 +2355,6 @@ void qmp_block_commit(const char *device,
>      aio_context = bdrv_get_aio_context(bs);
>      aio_context_acquire(aio_context);
>  
> -    /* drain all i/o before commits */
> -    bdrv_drain_all();
> -

Reviewed-by: Fam Zheng <famz@redhat.com>

>      if (bdrv_op_is_blocked(bs, BLOCK_OP_TYPE_COMMIT_SOURCE, errp)) {
>          goto out;
>      }
> --
> 2.4.1
> 
> 
> 

  reply	other threads:[~2015-05-29  1:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28 14:21 [Qemu-devel] [PATCH] blockdev: no need to drain in qmp_block_commit Paolo Bonzini
2015-05-29  1:44 ` Fam Zheng [this message]
2015-05-29 12:43 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-06-16  4:07 ` [Qemu-devel] " Jeff Cody

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=407042981.6042811.1432863881730.JavaMail.zimbra@redhat.com \
    --to=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).