From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, armbru@redhat.com, mreitz@redhat.com,
pkrempa@redhat.com, qemu-block@nongnu.org
Subject: Re: [PATCH v4 0/5] block: add block-dirty-bitmap-populate job
Date: Thu, 3 Sep 2020 09:50:06 +0300 [thread overview]
Message-ID: <b718ea63-76d6-1c9c-0b16-956ca1045735@virtuozzo.com> (raw)
In-Reply-To: <20200902181831.2570048-1-eblake@redhat.com>
02.09.2020 21:18, Eric Blake wrote:
> This is NOT the final version of this patch series, but I'm posting it
> to revive conversation on the topic while fixing it to compile on top
> of meson changes.
>
> v3 was: https://lists.gnu.org/archive/html/qemu-devel/2020-06/msg06258.html
>
> 001/5:[0025] [FC] 'block: add bitmap-populate job'
> 002/5:[----] [--] 'blockdev: combine DriveBackupState and BlockdevBackupState'
> 003/5:[0004] [FC] 'qmp: expose block-dirty-bitmap-populate'
> 004/5:[----] [--] 'iotests: move bitmap helpers into their own file'
> 005/5:[----] [-C] 'iotests: add 298 for block-dirty-bitmap-populate'
>
> I'm still trying to find the right QAPI contract (affects patch 1 and
> 3 for the qapi, and 5 for invoking the command in iotests), but right
> now, I'm leaning towards:
>
> { "execute": "block-dirty-bitmap-populate", "arguments": {
> "job-id": "job0", "node": "target_node", "name": "target_bitmap",
> "sources": [ { "pattern": "allocation", "node": "from_node" } ] } }
>
> which allows expansion into multiple sources, so that we can combine a
> populate action with a bitmap merge rather than having to do those as
> separate commands, like:
>
> { "execute": "block-dirty-bitmap-populate", "arguments": {
> "job-id": "job0", "node": "target_node", "name": "target_bitmap",
> "sources": [ { "pattern": "allocation", "node": "from_node" },
> { "pattern": "bitmap", "node": "from_node",
> "bitmap": "from_bitmap" } ] } }
(I see, this is not realized in v4)
What about multiple targets as well, as we discussed in v3?
>
> John Snow (5):
> block: add bitmap-populate job
> blockdev: combine DriveBackupState and BlockdevBackupState
> qmp: expose block-dirty-bitmap-populate
> iotests: move bitmap helpers into their own file
> iotests: add 298 for block-dirty-bitmap-populate
>
> qapi/block-core.json | 66 +
> qapi/job.json | 6 +-
> qapi/transaction.json | 2 +
> include/block/block.h | 1 +
> include/block/block_int.h | 21 +
> block/bitmap-populate.c | 207 ++
> blockdev.c | 104 +-
> blockjob.c | 3 +-
> MAINTAINERS | 1 +
> block/meson.build | 1 +
> tests/qemu-iotests/257 | 110 +-
> tests/qemu-iotests/298 | 232 ++
> tests/qemu-iotests/298.out | 4544 +++++++++++++++++++++++++++++++++
> tests/qemu-iotests/bitmaps.py | 131 +
> tests/qemu-iotests/group | 1 +
> 15 files changed, 5301 insertions(+), 129 deletions(-)
> create mode 100644 block/bitmap-populate.c
> create mode 100755 tests/qemu-iotests/298
> create mode 100644 tests/qemu-iotests/298.out
> create mode 100644 tests/qemu-iotests/bitmaps.py
>
--
Best regards,
Vladimir
next prev parent reply other threads:[~2020-09-03 6:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 18:18 [PATCH v4 0/5] block: add block-dirty-bitmap-populate job Eric Blake
2020-09-02 18:18 ` [PATCH v4 1/5] block: add bitmap-populate job Eric Blake
2020-09-08 8:53 ` Markus Armbruster
2020-09-02 18:18 ` [PATCH v4 2/5] blockdev: combine DriveBackupState and BlockdevBackupState Eric Blake
2020-09-03 6:55 ` Vladimir Sementsov-Ogievskiy
2020-09-02 18:18 ` [PATCH v4 3/5] qmp: expose block-dirty-bitmap-populate Eric Blake
2020-09-02 18:18 ` [PATCH v4 4/5] iotests: move bitmap helpers into their own file Eric Blake
2020-09-03 6:56 ` Vladimir Sementsov-Ogievskiy
2020-09-02 18:18 ` [PATCH v4 5/5] iotests: add 298 for block-dirty-bitmap-populate Eric Blake
2020-09-03 6:50 ` Vladimir Sementsov-Ogievskiy [this message]
2021-03-19 20:04 ` [PATCH v4 0/5] block: add block-dirty-bitmap-populate job Vladimir Sementsov-Ogievskiy
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=b718ea63-76d6-1c9c-0b16-956ca1045735@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@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).