From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: jsnow@redhat.com, famz@redhat.com, mreitz@redhat.com,
kwolf@redhat.com, jcody@redhat.com, stefanha@redhat.com,
den@openvz.org, vsementsov@virtuozzo.com
Subject: [Qemu-devel] [PATCH 0/5] backup improvements part 1
Date: Mon, 2 Oct 2017 17:39:14 +0300 [thread overview]
Message-ID: <20171002143919.207741-1-vsementsov@virtuozzo.com> (raw)
Hi all. Here is a continuation of my "new backup architecture" series,
The very first part, but it is meaningful itself.
01: was previously sent in other my series, but here is more correct
version, one mistake is fixed.
02: only rebased to new byte-based interfaces (by Eric), r-bs saved
03: changed to use hbitmap_next_zero, also a comment added to
none-mode (Fam)
04: commit message rewritten. The patch was controversial, but I need
it for further backup enhancement, so, let's continue the
discussion.
05: rebased, logic is not changed, r-bs saved
Vladimir Sementsov-Ogievskiy (5):
hbitmap: add next_zero function
backup: move from done_bitmap to copy_bitmap
backup: init copy_bitmap from sync_bitmap for incremental
backup: simplify non-dirty bits progress processing
backup: use copy_bitmap in incremental backup
include/block/dirty-bitmap.h | 1 +
include/qemu/hbitmap.h | 8 +++
block/backup.c | 117 ++++++++++++++++++++++++-------------------
block/dirty-bitmap.c | 5 ++
util/hbitmap.c | 29 +++++++++++
5 files changed, 108 insertions(+), 52 deletions(-)
--
2.11.1
next reply other threads:[~2017-10-02 14:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 14:39 Vladimir Sementsov-Ogievskiy [this message]
2017-10-02 14:39 ` [Qemu-devel] [PATCH 1/5] hbitmap: add next_zero function Vladimir Sementsov-Ogievskiy
2017-10-02 15:43 ` Eric Blake
2017-10-02 16:16 ` Vladimir Sementsov-Ogievskiy
2017-10-09 21:51 ` John Snow
2017-10-12 10:05 ` Vladimir Sementsov-Ogievskiy
2017-10-02 14:39 ` [Qemu-devel] [PATCH 2/5] backup: move from done_bitmap to copy_bitmap Vladimir Sementsov-Ogievskiy
2017-10-09 22:16 ` John Snow
2017-10-02 14:39 ` [Qemu-devel] [PATCH 3/5] backup: init copy_bitmap from sync_bitmap for incremental Vladimir Sementsov-Ogievskiy
2017-10-09 22:56 ` John Snow
2017-10-12 11:23 ` Vladimir Sementsov-Ogievskiy
2017-11-07 0:25 ` John Snow
2017-10-02 14:39 ` [Qemu-devel] [PATCH 4/5] backup: simplify non-dirty bits progress processing Vladimir Sementsov-Ogievskiy
2017-10-09 23:44 ` John Snow
2017-10-12 11:42 ` Vladimir Sementsov-Ogievskiy
2017-10-12 13:56 ` Eric Blake
2017-10-02 14:39 ` [Qemu-devel] [PATCH 5/5] backup: use copy_bitmap in incremental backup Vladimir Sementsov-Ogievskiy
2017-10-09 23:51 ` John Snow
2017-10-02 15:38 ` [Qemu-devel] [PATCH 0/5] backup improvements part 1 Eric Blake
2017-10-02 16:17 ` 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=20171002143919.207741-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@openvz.org \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).