From: Wen Congyang <wency@cn.fujitsu.com>
To: Changlong Xie <xiecl.fnst@cn.fujitsu.com>,
qemu devel <qemu-devel@nongnu.org>, Fam Zheng <famz@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: zhanghailiang <zhang.zhanghailiang@huawei.com>,
qemu block <qemu-block@nongnu.org>,
Jiang Yunhong <yunhong.jiang@intel.com>,
Dong Eddie <eddie.dong@intel.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Michael R. Hines" <mrhines@linux.vnet.ibm.com>,
Gonglei <arei.gonglei@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v16 0/8] Block replication for continuous checkpoints
Date: Thu, 24 Mar 2016 14:19:26 +0800 [thread overview]
Message-ID: <56F386EE.5020002@cn.fujitsu.com> (raw)
In-Reply-To: <1457692455-15994-1-git-send-email-xiecl.fnst@cn.fujitsu.com>
Ping....
On 03/11/2016 06:34 PM, Changlong Xie wrote:
> Block replication is a very important feature which is used for
> continuous checkpoints(for example: COLO).
>
> You can get the detailed information about block replication from here:
> http://wiki.qemu.org/Features/BlockReplication
>
> Usage:
> Please refer to docs/block-replication.txt
>
> This patch series is based on the following patch series:
> 1. http://lists.nongnu.org/archive/html/qemu-devel/2016-03/msg02319.html
>
> Patch status:
> 1. Acked patches: none
> 2. Reviewed patches: patch 4
> 3. Updated patches: patch 7, 8
>
> You can get the patch here:
> https://github.com/Pating/qemu/tree/changlox/block-replication-v16
>
> You can get the patch with framework here:
> https://github.com/Pating/qemu/tree/changlox/colo_framework_v15
>
> TODO:
> 1. Continuous block replication. It will be started after basic functions
> are accepted.
>
> Changs Log:
> V16:
> 1. Rebase to the newest codes
> 2. Address comments from Stefan & hailiang
> p3: we don't need this patch now
> p4: add "top-id" parameters for secondary
> p6: fix NULL pointer in replication callbacks, remove unnecessary typedefs,
> add doc comments that explain the semantics of Replication
> p7: Refactor AioContext for thread-safe, remove unnecessary get_top_bs()
> *Note*: I'm working on replication testcase now, will send out in V17
> V15:
> 1. Rebase to the newest codes
> 2. Fix typos and coding style addresed Eric's comments
> 3. Address Stefan's comments
> 1) Make backup_do_checkpoint public, drop the changes on BlockJobDriver
> 2) Update the message and description for [PATCH 4/9]
> 3) Make replication_(start/stop/do_checkpoint)_all as global interfaces
> 4) Introduce AioContext lock to protect start/stop/do_checkpoint callbacks
> 5) Use BdrvChild instead of holding on to BlockDriverState * pointers
> 4. Clear BDRV_O_INACTIVE for hidden disk's open_flags since commit 09e0c771
> 5. Introduce replication_get_error_all to check replication status
> 6. Remove useless discard interface
> V14:
> 1. Implement auto complete active commit
> 2. Implement active commit block job for replication.c
> 3. Address the comments from Stefan, add replication-specific API and data
> structure, also remove old block layer APIs
> V13:
> 1. Rebase to the newest codes
> 2. Remove redundant marcos and semicolon in replication.c
> 3. Fix typos in block-replication.txt
> V12:
> 1. Rebase to the newest codes
> 2. Use backing reference to replcace 'allow-write-backing-file'
> V11:
> 1. Reopen the backing file when starting blcok replication if it is not
> opened in R/W mode
> 2. Unblock BLOCK_OP_TYPE_BACKUP_SOURCE and BLOCK_OP_TYPE_BACKUP_TARGET
> when opening backing file
> 3. Block the top BDS so there is only one block job for the top BDS and
> its backing chain.
> V10:
> 1. Use blockdev-remove-medium and blockdev-insert-medium to replace backing
> reference.
> 2. Address the comments from Eric Blake
> V9:
> 1. Update the error messages
> 2. Rebase to the newest qemu
> 3. Split child add/delete support. These patches are sent in another patchset.
> V8:
> 1. Address Alberto Garcia's comments
> V7:
> 1. Implement adding/removing quorum child. Remove the option non-connect.
> 2. Simplify the backing refrence option according to Stefan Hajnoczi's suggestion
> V6:
> 1. Rebase to the newest qemu.
> V5:
> 1. Address the comments from Gong Lei
> 2. Speed the failover up. The secondary vm can take over very quickly even
> if there are too many I/O requests.
> V4:
> 1. Introduce a new driver replication to avoid touch nbd and qcow2.
> V3:
> 1: use error_setg() instead of error_set()
> 2. Add a new block job API
> 3. Active disk, hidden disk and nbd target uses the same AioContext
> 4. Add a testcase to test new hbitmap API
> V2:
> 1. Redesign the secondary qemu(use image-fleecing)
> 2. Use Error objects to return error message
> 3. Address the comments from Max Reitz and Eric Blake
>
> Changlong Xie (1):
> Introduce new APIs to do replication operation
>
> Wen Congyang (7):
> unblock backup operations in backing file
> Backup: clear all bitmap when doing block checkpoint
> Link backup into block core
> docs: block replication's description
> auto complete active commit
> Implement new driver for block replication
> support replication driver in blockdev-add
>
> Makefile.objs | 1 +
> block.c | 18 ++
> block/Makefile.objs | 3 +-
> block/backup.c | 15 ++
> block/mirror.c | 13 +-
> block/replication.c | 619 +++++++++++++++++++++++++++++++++++++++++++++
> blockdev.c | 2 +-
> docs/block-replication.txt | 238 +++++++++++++++++
> include/block/block_int.h | 5 +-
> qapi/block-core.json | 33 ++-
> qemu-img.c | 2 +-
> replication.c | 94 +++++++
> replication.h | 175 +++++++++++++
> 13 files changed, 1208 insertions(+), 10 deletions(-)
> create mode 100644 block/replication.c
> create mode 100644 docs/block-replication.txt
> create mode 100644 replication.c
> create mode 100644 replication.h
>
prev parent reply other threads:[~2016-03-24 6:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 10:34 [Qemu-devel] [PATCH v16 0/8] Block replication for continuous checkpoints Changlong Xie
2016-03-11 10:34 ` [Qemu-devel] [PATCH v16 1/8] unblock backup operations in backing file Changlong Xie
2016-03-11 10:34 ` [Qemu-devel] [PATCH v16 2/8] Backup: clear all bitmap when doing block checkpoint Changlong Xie
2016-03-16 18:48 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2016-03-17 1:22 ` Changlong Xie
2016-03-11 10:34 ` [Qemu-devel] [PATCH v16 3/8] Link backup into block core Changlong Xie
2016-03-11 10:34 ` [Qemu-devel] [PATCH v16 4/8] docs: block replication's description Changlong Xie
2016-03-28 6:14 ` Changlong Xie
2016-03-11 10:34 ` [Qemu-devel] [PATCH v16 5/8] auto complete active commit Changlong Xie
2016-03-11 10:34 ` [Qemu-devel] [PATCH v16 6/8] Introduce new APIs to do replication operation Changlong Xie
2016-03-11 10:34 ` [Qemu-devel] [PATCH v16 7/8] Implement new driver for block replication Changlong Xie
2016-03-11 10:34 ` [Qemu-devel] [PATCH v16 8/8] support replication driver in blockdev-add Changlong Xie
2016-03-24 6:19 ` Wen Congyang [this message]
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=56F386EE.5020002@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=mrhines@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=xiecl.fnst@cn.fujitsu.com \
--cc=yunhong.jiang@intel.com \
--cc=zhang.zhanghailiang@huawei.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).