From: Fam Zheng <famz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: kwolf@redhat.com, den@virtuozzo.com, jsnow@redhat.com,
qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/6] external backup api
Date: Wed, 3 Feb 2016 16:14:18 +0800 [thread overview]
Message-ID: <20160203081418.GC25746@ad.usersys.redhat.com> (raw)
In-Reply-To: <1454151394-52320-1-git-send-email-vsementsov@virtuozzo.com>
On Sat, 01/30 13:56, Vladimir Sementsov-Ogievskiy wrote:
> Hi all.
>
> These series which aims to add external backup api. This is needed to allow
> backup software use our dirty bitmaps.
>
> Vmware and Parallels Cloud Server have this feature.
What is the advantage of this appraoch over "drive-backup sync=incremental
..."?
>
> There are three things are done:
> - add query-block-dirty-bitmap-ranges qmp command
> - add qmp commands for dirty-bitmap functions: create_successor, abdicate,
> reclaim.
> - make create-successor command transaction-able
>
> Then, external backup should be done like this:
>
> 1. qmp transaction {
> external-snapshot
> bitmap-create-successor
> }
>
> 2. qmp query frozen bitmap, not acquiring aio context.
What do you do with the query response, read the snapshot image with an
external tool?
Fam
>
> 3. do external backup, using snapshot and bitmap
>
>
> 4. if (success backup)
> qmp bitmap-abdicate
> else
> qmp bitmap-reclaime
>
> 5. qmp merge snapshot
>
>
> v2: a lot of additions and changes, no sense to compare with v1
>
>
> Vladimir Sementsov-Ogievskiy (6):
> block dirty bitmap: add next_zero function
> qmp: add query-block-dirty-bitmap-ranges
> iotests: test query-block-dirty-bitmap-ranges
> qapi: add qmp commands for some dirty bitmap functions
> qapi: make block-dirty-bitmap-create-successor transaction-able
> iotests: test external backup api
>
> block/dirty-bitmap.c | 60 ++++++++++++++++++++++
> blockdev.c | 113 +++++++++++++++++++++++++++++++++++++++++
> include/block/dirty-bitmap.h | 9 ++++
> include/qemu/hbitmap.h | 8 +++
> qapi-schema.json | 4 +-
> qapi/block-core.json | 90 +++++++++++++++++++++++++++++++++
> qmp-commands.hx | 118 +++++++++++++++++++++++++++++++++++++++++++
> tests/qemu-iotests/150 | 88 ++++++++++++++++++++++++++++++++
> tests/qemu-iotests/150.out | 21 ++++++++
> tests/qemu-iotests/151 | 77 ++++++++++++++++++++++++++++
> tests/qemu-iotests/151.out | 7 +++
> tests/qemu-iotests/group | 2 +
> util/hbitmap.c | 26 ++++++++++
> 13 files changed, 622 insertions(+), 1 deletion(-)
> create mode 100755 tests/qemu-iotests/150
> create mode 100644 tests/qemu-iotests/150.out
> create mode 100755 tests/qemu-iotests/151
> create mode 100644 tests/qemu-iotests/151.out
>
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2016-02-03 8:14 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 10:56 [Qemu-devel] [PATCH v2 0/6] external backup api Vladimir Sementsov-Ogievskiy
2016-01-30 10:56 ` [Qemu-devel] [PATCH 1/6] block dirty bitmap: add next_zero function Vladimir Sementsov-Ogievskiy
2016-01-30 10:56 ` [Qemu-devel] [PATCH 2/6] qmp: add query-block-dirty-bitmap-ranges Vladimir Sementsov-Ogievskiy
2016-02-10 10:08 ` Stefan Hajnoczi
2016-02-10 13:57 ` Denis V. Lunev
2016-02-10 15:26 ` John Snow
2016-02-10 15:36 ` Denis V. Lunev
2016-02-10 15:37 ` John Snow
2016-02-10 15:40 ` Denis V. Lunev
2016-02-14 5:05 ` Fam Zheng
2016-01-30 10:56 ` [Qemu-devel] [PATCH 3/6] iotests: test query-block-dirty-bitmap-ranges Vladimir Sementsov-Ogievskiy
2016-01-30 10:56 ` [Qemu-devel] [PATCH 4/6] qapi: add qmp commands for some dirty bitmap functions Vladimir Sementsov-Ogievskiy
2016-01-30 10:56 ` [Qemu-devel] [PATCH 5/6] qapi: make block-dirty-bitmap-create-successor transaction-able Vladimir Sementsov-Ogievskiy
2016-01-30 10:56 ` [Qemu-devel] [PATCH 6/6] iotests: test external backup api Vladimir Sementsov-Ogievskiy
2016-02-03 8:14 ` Fam Zheng [this message]
2016-02-03 10:57 ` [Qemu-devel] [PATCH v2 0/6] " Vladimir Sementsov-Ogievskiy
2016-02-03 11:02 ` Fam Zheng
2016-02-03 11:24 ` Vladimir Sementsov-Ogievskiy
2016-02-05 8:28 ` Denis V. Lunev
2016-02-05 8:44 ` Fam Zheng
2016-02-09 14:21 ` Stefan Hajnoczi
2016-02-09 14:37 ` Denis V. Lunev
2016-02-09 16:49 ` John Snow
2016-02-09 16:58 ` Denis V. Lunev
2016-02-09 18:12 ` John Snow
2016-02-09 19:25 ` Denis V. Lunev
2016-02-10 8:04 ` Denis V. Lunev
2016-02-09 14:28 ` Stefan Hajnoczi
2016-02-09 14:41 ` Denis V. Lunev
2016-02-10 10:10 ` Stefan Hajnoczi
2016-02-16 17:09 ` Stefan Hajnoczi
2016-02-16 17:17 ` Vladimir Sementsov-Ogievskiy
2016-02-16 17:20 ` Denis V. Lunev
2016-02-18 16:39 ` Stefan Hajnoczi
2016-02-18 17:07 ` Markus Armbruster
2016-02-17 17:47 ` Vladimir Sementsov-Ogievskiy
2016-02-18 0:59 ` Fam Zheng
2016-02-18 12:11 ` Daniel P. Berrange
2016-02-18 16:41 ` Stefan Hajnoczi
2016-02-19 2:08 ` Fam Zheng
2016-02-19 8:51 ` Markus Armbruster
2016-02-24 23:34 ` John Snow
2016-02-26 19:55 ` Paolo Bonzini
2016-02-26 20:03 ` Paolo Bonzini
2016-02-26 20:29 ` Denis V. Lunev
2016-02-26 21:37 ` John Snow
2016-02-26 20:40 ` Denis V. Lunev
2016-02-27 4:26 ` Fam Zheng
2016-02-29 8:14 ` Markus Armbruster
2016-02-29 8:54 ` Paolo Bonzini
2016-02-29 9:42 ` Paolo Bonzini
2016-02-29 10:05 ` Fam Zheng
2016-03-10 17:37 ` Stefan Hajnoczi
2016-03-10 17:40 ` Paolo Bonzini
2016-03-14 16:27 ` Denis V. Lunev
2016-02-29 10:22 ` Markus Armbruster
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=20160203081418.GC25746@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=den@virtuozzo.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).