From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: mreitz@redhat.com, kwolf@redhat.com, jsnow@redhat.com,
vsementsov@virtuozzo.com, den@openvz.org
Subject: [Qemu-devel] [PATCH v7 0/5] backup-top: preparing refactoring
Date: Mon, 29 Apr 2019 12:08:37 +0300 [thread overview]
Message-ID: <20190429090842.57910-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Here some refactoring patches, as a first step for backup-top filter
introduction.
v7:
01,03,04: add Max's r-b
05: fix s/return NULL/goto error/ [Max]
v6:
01: - use end_cluster instead of last_cluster and fix bug in
calculation [Max]
02: only rebased on 01, keep r-b
03, 04: new
05: it's rewritten
"[PATCH v5 10/11] block/backup: tiny refactor backup_job_create",
to make it more useful in general than just code movement inside
one function
Vladimir Sementsov-Ogievskiy (5):
block/backup: simplify backup_incremental_init_copy_bitmap
block/backup: move to copy_bitmap with granularity
block/backup: refactor and tolerate unallocated cluster skipping
block/backup: unify different modes code path
block/backup: refactor: split out backup_calculate_cluster_size
block/backup.c | 243 +++++++++++++++++++++----------------------------
1 file changed, 105 insertions(+), 138 deletions(-)
--
2.18.0
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, den@openvz.org, vsementsov@virtuozzo.com,
jsnow@redhat.com, mreitz@redhat.com
Subject: [Qemu-devel] [PATCH v7 0/5] backup-top: preparing refactoring
Date: Mon, 29 Apr 2019 12:08:37 +0300 [thread overview]
Message-ID: <20190429090842.57910-1-vsementsov@virtuozzo.com> (raw)
Message-ID: <20190429090837.FscOWZ80J6NX_S2mqo3yfOeO7QiKl2Tj7tSjSddKXBs@z> (raw)
Hi all!
Here some refactoring patches, as a first step for backup-top filter
introduction.
v7:
01,03,04: add Max's r-b
05: fix s/return NULL/goto error/ [Max]
v6:
01: - use end_cluster instead of last_cluster and fix bug in
calculation [Max]
02: only rebased on 01, keep r-b
03, 04: new
05: it's rewritten
"[PATCH v5 10/11] block/backup: tiny refactor backup_job_create",
to make it more useful in general than just code movement inside
one function
Vladimir Sementsov-Ogievskiy (5):
block/backup: simplify backup_incremental_init_copy_bitmap
block/backup: move to copy_bitmap with granularity
block/backup: refactor and tolerate unallocated cluster skipping
block/backup: unify different modes code path
block/backup: refactor: split out backup_calculate_cluster_size
block/backup.c | 243 +++++++++++++++++++++----------------------------
1 file changed, 105 insertions(+), 138 deletions(-)
--
2.18.0
next reply other threads:[~2019-04-29 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 9:08 Vladimir Sementsov-Ogievskiy [this message]
2019-04-29 9:08 ` [Qemu-devel] [PATCH v7 0/5] backup-top: preparing refactoring Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` [Qemu-devel] [PATCH v7 1/5] block/backup: simplify backup_incremental_init_copy_bitmap Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` [Qemu-devel] [PATCH v7 2/5] block/backup: move to copy_bitmap with granularity Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` [Qemu-devel] [PATCH v7 3/5] block/backup: refactor and tolerate unallocated cluster skipping Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` [Qemu-devel] [PATCH v7 4/5] block/backup: unify different modes code path Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` [Qemu-devel] [PATCH v7 5/5] block/backup: refactor: split out backup_calculate_cluster_size Vladimir Sementsov-Ogievskiy
2019-04-29 9:08 ` Vladimir Sementsov-Ogievskiy
2019-05-09 16:12 ` Max Reitz
2019-05-13 9:54 ` Vladimir Sementsov-Ogievskiy
2019-05-13 13:41 ` [Qemu-devel] [PATCH v7 0/5] backup-top: preparing refactoring 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=20190429090842.57910-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.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 \
/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).