From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, fam@euphon.net, stefanha@redhat.com,
eblake@redhat.com, vsementsov@virtuozzo.com, jsnow@redhat.com,
hreitz@redhat.com, kwolf@redhat.com
Subject: [PATCH 0/4] block/dirty-bitmaps: fix and improve bitmap merge
Date: Tue, 15 Feb 2022 18:53:06 +0100 [thread overview]
Message-ID: <20220215175310.68058-1-vsementsov@virtuozzo.com> (raw)
Hi all!
Here are some good refactoring and fix of bitmap merge paths.
Vladimir Sementsov-Ogievskiy (4):
block: bdrv_merge_dirty_bitmap: add return value
block: block_dirty_bitmap_merge(): fix error path
block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap
block: simplify handling of try to merge different sized bitmaps
include/block/block_int.h | 2 +-
include/block/dirty-bitmap.h | 2 +-
include/qemu/hbitmap.h | 15 ++-------------
block/backup.c | 6 ++----
block/dirty-bitmap.c | 31 ++++++++++++++-----------------
block/monitor/bitmap-qmp-cmds.c | 31 +++++++++----------------------
util/hbitmap.c | 25 +++++++------------------
7 files changed, 36 insertions(+), 76 deletions(-)
--
2.31.1
next reply other threads:[~2022-02-15 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 17:53 Vladimir Sementsov-Ogievskiy [this message]
2022-02-15 17:53 ` [PATCH 1/4] block: bdrv_merge_dirty_bitmap: add return value Vladimir Sementsov-Ogievskiy
2022-02-16 8:50 ` Vladimir Sementsov-Ogievskiy
2022-02-15 17:53 ` [PATCH 2/4] block: block_dirty_bitmap_merge(): fix error path Vladimir Sementsov-Ogievskiy
2022-02-19 10:26 ` Nikta Lapshin
2022-02-15 17:53 ` [PATCH 3/4] block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap Vladimir Sementsov-Ogievskiy
2022-02-19 10:29 ` Nikta Lapshin
2022-02-21 15:59 ` Vladimir Sementsov-Ogievskiy
2022-02-15 17:53 ` [PATCH 4/4] block: simplify handling of try to merge different sized bitmaps Vladimir Sementsov-Ogievskiy
2022-02-19 11:04 ` Nikta Lapshin
2022-02-19 14:07 ` Vladimir Sementsov-Ogievskiy via
2022-02-22 16:15 ` 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=20220215175310.68058-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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).