From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, vsementsov@virtuozzo.com,
wencongyang2@huawei.com, xiechanglong.d@gmail.com,
qemu-devel@nongnu.org, armbru@redhat.com, den@openvz.org,
mreitz@redhat.com, jsnow@redhat.com
Subject: [PATCH v15 0/5] backup-top filter driver for backup
Date: Tue, 1 Oct 2019 16:14:04 +0300 [thread overview]
Message-ID: <20191001131409.14202-1-vsementsov@virtuozzo.com> (raw)
Hi all!
These series introduce backup-top driver. It's a filter-node, which
do copy-before-write operation. Mirror uses filter-node for handling
guest writes, let's move to filter-node (from write-notifiers) for
backup too.
Preparation patches are queued in Max's block branch:
Based-on: https://github.com/XanClic/qemu.git block
v15: use BdrvChildren in block-copy
01-03: new
04-05: a lot of changes, such as
04:
- add new parameters for creation
- prepare bcs creation
- add target child
- refactor bdrv_backup_top_append
- drop r-b
05:
- move block-copy to use BdrvChildren
- drop extra style fixing hunks
- iotest 141 output changed
v14: Drop range locks, keep old good in-flight requests waiting
12: new patch
14: use old request-waiting scheme instead of range locks
Vladimir Sementsov-Ogievskiy (5):
block/backup: move in-flight requests handling from backup to
block-copy
block/backup: move write_flags calculation inside backup_job_create
block/block-copy: split block_copy_set_callbacks function
block: introduce backup-top filter driver
block/backup: use backup-top instead of write notifiers
qapi/block-core.json | 8 +-
block/backup-top.h | 41 +++++
include/block/block-copy.h | 31 +++-
include/block/block_int.h | 1 +
block/backup-top.c | 276 +++++++++++++++++++++++++++++++++
block/backup.c | 147 +++++-------------
block/block-copy.c | 140 +++++++++--------
block/replication.c | 2 +-
blockdev.c | 1 +
block/Makefile.objs | 1 +
tests/qemu-iotests/056 | 8 +-
tests/qemu-iotests/141.out | 2 +-
tests/qemu-iotests/257 | 7 +-
tests/qemu-iotests/257.out | 306 ++++++++++++++++++-------------------
14 files changed, 628 insertions(+), 343 deletions(-)
create mode 100644 block/backup-top.h
create mode 100644 block/backup-top.c
--
2.21.0
next reply other threads:[~2019-10-01 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 13:14 Vladimir Sementsov-Ogievskiy [this message]
2019-10-01 13:14 ` [PATCH v15 1/5] block/backup: move in-flight requests handling from backup to block-copy Vladimir Sementsov-Ogievskiy
2019-10-02 18:09 ` Max Reitz
2019-10-01 13:14 ` [PATCH v15 2/5] block/backup: move write_flags calculation inside backup_job_create Vladimir Sementsov-Ogievskiy
2019-10-02 18:35 ` Max Reitz
2019-10-01 13:14 ` [PATCH v15 3/5] block/block-copy: split block_copy_set_callbacks function Vladimir Sementsov-Ogievskiy
2019-10-02 18:43 ` Max Reitz
2019-10-01 13:14 ` [PATCH v15 4/5] block: introduce backup-top filter driver Vladimir Sementsov-Ogievskiy
2019-10-04 13:37 ` Max Reitz
2019-10-01 13:14 ` [PATCH v15 5/5] block/backup: use backup-top instead of write notifiers Vladimir Sementsov-Ogievskiy
2019-10-04 14:19 ` Max Reitz
2019-10-04 14:21 ` [PATCH v15 0/5] backup-top filter driver for backup Max Reitz
2019-10-04 14:36 ` 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=20191001131409.14202-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wencongyang2@huawei.com \
--cc=xiechanglong.d@gmail.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).