From: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
To: Kevin Wolf <kwolf@redhat.com>,
Vladimir Sementsov-Ogievskiy
<vladimir.sementsov-ogievskiy@openvz.org>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, eblake@redhat.com,
hreitz@redhat.com, jsnow@redhat.com, vsementsov@openvz.org,
nikita.lapshin@virtuozzo.com
Subject: Re: [PATCH v3 2/3] block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap
Date: Tue, 17 May 2022 13:36:17 +0300 [thread overview]
Message-ID: <ff4edfe2-29a7-9b31-0cfd-5e54b20b17a0@mail.ru> (raw)
In-Reply-To: <YnD00CJqxBT/hM2T@redhat.com>
03.05.2022 12:24, Kevin Wolf wrote:
> Am 01.04.2022 um 12:08 hat Vladimir Sementsov-Ogievskiy geschrieben:
>> We don't need extra bitmap. All we need is to backup the original
>> bitmap when we do first merge. So, drop extra temporary bitmap and work
>> directly with target and backup.
>>
>> Still to keep old semantics, that on failure target is unchanged and
>> user don't need to restore, we need a local_backup variable and do
>> restore ourselves on failure path.
>>
>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@openvz.org>
>> ---
>> block/monitor/bitmap-qmp-cmds.c | 39 ++++++++++++++++-----------------
>> 1 file changed, 19 insertions(+), 20 deletions(-)
>>
>> diff --git a/block/monitor/bitmap-qmp-cmds.c b/block/monitor/bitmap-qmp-cmds.c
>> index 4db704c015..07d0da323b 100644
>> --- a/block/monitor/bitmap-qmp-cmds.c
>> +++ b/block/monitor/bitmap-qmp-cmds.c
>> @@ -261,8 +261,9 @@ BdrvDirtyBitmap *block_dirty_bitmap_merge(const char *node, const char *target,
>> HBitmap **backup, Error **errp)
>> {
>> BlockDriverState *bs;
>> - BdrvDirtyBitmap *dst, *src, *anon;
>> + BdrvDirtyBitmap *dst, *src;
>> BlockDirtyBitmapMergeSourceList *lst;
>> + HBitmap *local_backup = NULL;
>>
>> GLOBAL_STATE_CODE();
>>
>> @@ -271,12 +272,6 @@ BdrvDirtyBitmap *block_dirty_bitmap_merge(const char *node, const char *target,
>> return NULL;
>> }
>>
>> - anon = bdrv_create_dirty_bitmap(bs, bdrv_dirty_bitmap_granularity(dst),
>> - NULL, errp);
>> - if (!anon) {
>> - return NULL;
>> - }
>> -
>> for (lst = bms; lst; lst = lst->next) {
>> switch (lst->value->type) {
>> const char *name, *node;
>> @@ -285,8 +280,7 @@ BdrvDirtyBitmap *block_dirty_bitmap_merge(const char *node, const char *target,
>> src = bdrv_find_dirty_bitmap(bs, name);
>> if (!src) {
>> error_setg(errp, "Dirty bitmap '%s' not found", name);
>> - dst = NULL;
>> - goto out;
>> + goto fail;
>> }
>> break;
>> case QTYPE_QDICT:
>> @@ -294,29 +288,34 @@ BdrvDirtyBitmap *block_dirty_bitmap_merge(const char *node, const char *target,
>> name = lst->value->u.external.name;
>> src = block_dirty_bitmap_lookup(node, name, NULL, errp);
>> if (!src) {
>> - dst = NULL;
>> - goto out;
>> + goto fail;
>> }
>> break;
>> default:
>> abort();
>> }
>>
>> - if (!bdrv_merge_dirty_bitmap(anon, src, NULL, errp)) {
>> - dst = NULL;
>> - goto out;
>> + /* We do backup only for first merge operation */
>> + if (!bdrv_merge_dirty_bitmap(dst, src,
>> + local_backup ? NULL : &local_backup,
>> + errp))
>> + {
>> + goto fail;
>> }
>> }
>>
>> - /* Merge into dst; dst is unchanged on failure. */
>> - if (!bdrv_merge_dirty_bitmap(dst, anon, backup, errp)) {
>> - dst = NULL;
>> - goto out;
>> + if (backup) {
>> + *backup = local_backup;
>> }
>
> Don't we need something like '... else { hbitmap_free(local_backup); }'
> in order to avoid leaking the memory?
Right! Will resend.
>
>>
>> - out:
>> - bdrv_release_dirty_bitmap(anon);
>> return dst;
>> +
>> +fail:
>> + if (local_backup) {
>> + bdrv_restore_dirty_bitmap(dst, local_backup);
>> + }
>> +
>> + return NULL;
>> }
>
> Kevin
>
--
Best regards,
Vladimir
next prev parent reply other threads:[~2022-05-17 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 10:08 [PATCH v3 0/3] block/dirty-bitmaps: fix and improve bitmap merge Vladimir Sementsov-Ogievskiy
2022-04-01 10:08 ` [PATCH v3 1/3] block: block_dirty_bitmap_merge(): fix error path Vladimir Sementsov-Ogievskiy
2022-05-03 9:27 ` Kevin Wolf
2022-04-01 10:08 ` [PATCH v3 2/3] block: improve block_dirty_bitmap_merge(): don't allocate extra bitmap Vladimir Sementsov-Ogievskiy
2022-05-03 9:24 ` Kevin Wolf
2022-05-17 10:36 ` Vladimir Sementsov-Ogievskiy [this message]
2022-04-01 10:08 ` [PATCH v3 3/3] block: simplify handling of try to merge different sized bitmaps Vladimir Sementsov-Ogievskiy
2022-05-03 9:34 ` Kevin Wolf
2022-04-01 15:08 ` [PATCH v3 0/3] block/dirty-bitmaps: fix and improve bitmap merge Hanna Reitz
2022-04-01 20:17 ` Eric Blake
2022-04-01 21:06 ` 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=ff4edfe2-29a7-9b31-0cfd-5e54b20b17a0@mail.ru \
--to=v.sementsov-og@mail.ru \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=nikita.lapshin@virtuozzo.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vladimir.sementsov-ogievskiy@openvz.org \
--cc=vsementsov@openvz.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).