From: Max Reitz <mreitz@redhat.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, John Snow <jsnow@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [RFC qemu 0/6] mirror: implement incremental and bitmap modes
Date: Fri, 21 Aug 2020 15:03:37 +0200 [thread overview]
Message-ID: <d35a76de-78d5-af56-0b34-f7bd2bbd3733@redhat.com> (raw)
In-Reply-To: <20200218100740.2228521-1-f.gruenbichler@proxmox.com>
[-- Attachment #1.1: Type: text/plain, Size: 1314 bytes --]
On 18.02.20 11:07, Fabian Grünbichler wrote:
[Sorry :/]
> picking up on John's in-progress patch series from last summer, this is
> a stab at rebasing and adding test cases for the low-hanging fruits:
>
> - bitmap mirror mode with always/on-success/never bitmap sync mode
> - incremental mirror mode as sugar for bitmap + on-success
>
> Fabian Grünbichler (4):
> mirror: add check for bitmap-mode without bitmap
> mirror: switch to bdrv_dirty_bitmap_merge_internal
> iotests: add test for bitmap mirror
> mirror: move some checks to QMP
>
> John Snow (2):
> drive-mirror: add support for sync=bitmap mode=never
> drive-mirror: add support for conditional and always bitmap sync modes
Looks reasonable to me. I would indeed merge patches 2 through 4 into a
single one, and perhaps switch patches 5 and 6.
Also, we still need an S-o-b from John on patch 2.
I have one question: When the mirror job completes successfully (or is
cancelled “successfully”), the bitmap is always fully cleared when the
job completes, right? (Unless in “never” mode.)
Not that I think we should change the current implementation of “clear
sync_bitmap; merge dirty_bitmap into sync_bitmap;”. Just a question for
understanding.
Soo... What’s the plan?
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-21 13:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 10:07 [RFC qemu 0/6] mirror: implement incremental and bitmap modes Fabian Grünbichler
2020-02-18 10:07 ` [RFC qemu 1/6] drive-mirror: add support for sync=bitmap mode=never Fabian Grünbichler
2020-02-18 10:07 ` [RFC qemu 2/6] drive-mirror: add support for conditional and always bitmap sync modes Fabian Grünbichler
2020-02-18 10:07 ` [RFC qemu 3/6] mirror: add check for bitmap-mode without bitmap Fabian Grünbichler
2020-02-18 10:07 ` [RFC qemu 4/6] mirror: switch to bdrv_dirty_bitmap_merge_internal Fabian Grünbichler
2020-02-18 10:07 ` [RFC qemu 5/6] iotests: add test for bitmap mirror Fabian Grünbichler
2020-02-18 10:07 ` [RFC qemu 6/6] mirror: move some checks to QMP Fabian Grünbichler
2020-02-18 10:43 ` [RFC qemu 0/6] mirror: implement incremental and bitmap modes no-reply
2020-02-25 21:54 ` John Snow
2020-04-03 11:34 ` Fabian Grünbichler
2020-08-21 13:03 ` Max Reitz [this message]
2020-08-24 15:54 ` John Snow
2020-09-03 10:13 ` Fabian Grünbichler
2020-09-03 11:04 ` Max Reitz
2020-09-03 12:38 ` Kevin Wolf
2020-09-03 12:57 ` Max Reitz
2020-09-03 13:23 ` Kevin Wolf
2020-09-03 13:36 ` Fabian Grünbichler
2020-09-03 13:43 ` Kevin Wolf
2020-09-03 13:51 ` Max Reitz
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=d35a76de-78d5-af56-0b34-f7bd2bbd3733@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=f.gruenbichler@proxmox.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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).