From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>
Cc: jcody@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 11/12] qed: Implement .bdrv_drain
Date: Thu, 22 Oct 2015 22:59:32 +0200 [thread overview]
Message-ID: <56294E34.1080805@redhat.com> (raw)
In-Reply-To: <20151022105345.GF3941@noname.redhat.com>
On 22/10/2015 12:53, Kevin Wolf wrote:
> Am 22.10.2015 um 08:32 hat Fam Zheng geschrieben:
>> The "need_check_timer" is used to clear the "NEED_CHECK" flag in the
>> image header after a grace period once metadata update has finished. In
>> compliance to the bdrv_drain semantics we should make sure it remains
>> deleted once .bdrv_drain is called.
>>
>> We cannot reuse qed_need_check_timer_cb because it calls bdrv_aio_flush
>> with a completion callback that starts more I/O, bdrv_drain cannot cope
>> with this.
>
> For the record: I discussed this with Fam on IRC and we came to the
> conclusion that we should instead fix bdrv_drain() to correctly drain
> in-flight flushes.
>
> In order to achieve this, Fam will send a series that adds a
> BdrvTrackedRequest to all remaining asynchronous operations. So far we
> have identified flush, discard and aio_ioctl. At the same time he will
> send a rebased version of this series that goes back to asynchronous
> flushing in bdrv_qed_drain().
This is a completely separate bug. Can you at least merge all patches
except this, so that everything except QED can do snapshots with
dataplane? Of course there will be a v7 at least for patch 9.
Paolo
next prev parent reply other threads:[~2015-10-22 20:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 6:32 [Qemu-devel] [PATCH v6 00/12] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 01/12] aio: Add "is_external" flag for event handlers Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 02/12] nbd: Mark fd handlers client type as "external" Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 03/12] dataplane: Mark host notifiers' " Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 04/12] aio: introduce aio_{disable, enable}_external Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 05/12] block: Introduce "drained begin/end" API Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 06/12] block: Add "drained begin/end" for transactional external snapshot Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 07/12] block: Add "drained begin/end" for transactional backup Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 08/12] block: Add "drained begin/end" for transactional blockdev-backup Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 09/12] block: Add "drained begin/end" for internal snapshot Fam Zheng
2015-10-22 10:18 ` Kevin Wolf
2015-10-22 11:05 ` Jeff Cody
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 10/12] block: Introduce BlockDriver.bdrv_drain callback Fam Zheng
2015-10-22 6:32 ` [Qemu-devel] [PATCH v6 11/12] qed: Implement .bdrv_drain Fam Zheng
2015-10-22 10:53 ` Kevin Wolf
2015-10-22 20:59 ` Paolo Bonzini [this message]
2015-10-23 3:07 ` Fam Zheng
2015-10-22 6:33 ` [Qemu-devel] [PATCH v6 12/12] tests: Add test case for aio_disable_external Fam Zheng
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=56294E34.1080805@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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.