From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
"jsnow@redhat.com" <jsnow@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mreitz@redhat.com" <mreitz@redhat.com>
Subject: Re: [PATCH v2 00/10] Further bitmaps improvements
Date: Thu, 14 Nov 2019 18:51:57 +0000 [thread overview]
Message-ID: <d0039f5d-9877-59f0-218d-a3a8f41e096f@virtuozzo.com> (raw)
In-Reply-To: <4aec835a-a894-03a0-11e4-0407e0f18a84@redhat.com>
14.11.2019 21:47, Eric Blake wrote:
> On 10/22/19 7:58 AM, Vladimir Sementsov-Ogievskiy wrote:
>> Hi!
>>
>> The main feature here is improvement of _next_dirty_area API, which I'm
>> going to use then for backup / block-copy.
>>
>> v2:
>> 01: just use INT64_MAX instead of adding new constant
>> 08: add separate function nbd_extent_array_convert_to_be and converted
>> state of NBDExtentArray, to make these things explicit, and avoid
>> extra memdup.
>> 09: Save part of comment for bitmap_to_extents(), add Eric's r-b
>
> Is any of this series a bug fix important to get into -rc2?
Nothing
> Or is it safe to defer to the 5.0 timeframe?
Yes, no doubts.
>
>>
>> Vladimir Sementsov-Ogievskiy (10):
>> hbitmap: assert that we don't create bitmap larger than INT64_MAX
>> hbitmap: move hbitmap_iter_next_word to hbitmap.c
>> hbitmap: unpublish hbitmap_iter_skip_words
>> hbitmap: drop meta bitmaps as they are unused
>> block/dirty-bitmap: switch _next_dirty_area and _next_zero to int64_t
>> block/dirty-bitmap: add _next_dirty API
>> block/dirty-bitmap: improve _next_dirty_area API
>> nbd/server: introduce NBDExtentArray
>> nbd/server: use bdrv_dirty_bitmap_next_dirty_area
>> block/qcow2-bitmap: use bdrv_dirty_bitmap_next_dirty
>>
>
--
Best regards,
Vladimir
prev parent reply other threads:[~2019-11-14 18:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 12:58 [PATCH v2 00/10] Further bitmaps improvements Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 01/10] hbitmap: assert that we don't create bitmap larger than INT64_MAX Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 02/10] hbitmap: move hbitmap_iter_next_word to hbitmap.c Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 03/10] hbitmap: unpublish hbitmap_iter_skip_words Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 04/10] hbitmap: drop meta bitmaps as they are unused Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 05/10] block/dirty-bitmap: switch _next_dirty_area and _next_zero to int64_t Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 06/10] block/dirty-bitmap: add _next_dirty API Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 07/10] block/dirty-bitmap: improve _next_dirty_area API Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 08/10] nbd/server: introduce NBDExtentArray Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 09/10] nbd/server: use bdrv_dirty_bitmap_next_dirty_area Vladimir Sementsov-Ogievskiy
2019-10-22 12:58 ` [PATCH v2 10/10] block/qcow2-bitmap: use bdrv_dirty_bitmap_next_dirty Vladimir Sementsov-Ogievskiy
2019-11-14 18:47 ` [PATCH v2 00/10] Further bitmaps improvements Eric Blake
2019-11-14 18:51 ` Vladimir Sementsov-Ogievskiy [this message]
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=d0039f5d-9877-59f0-218d-a3a8f41e096f@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=eblake@redhat.com \
--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).