From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, jsnow@redhat.com,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 00/15] Dirty bitmap changes for migration/persistence work
Date: Thu, 2 Jun 2016 14:43:11 +0300 [thread overview]
Message-ID: <57501BCF.203@virtuozzo.com> (raw)
In-Reply-To: <20160526004736.GA8286@ad.usersys.redhat.com>
Hi, what are the plans?
On 26.05.2016 03:47, Fam Zheng wrote:
> On Wed, 05/25 17:45, Vladimir Sementsov-Ogievskiy wrote:
>> Hi!
>>
>> Are you going to update the series in the near future?
> Yes, probably in a couple days.
>
> Fam
>
>> On 08.03.2016 07:44, Fam Zheng wrote:
>>> v4: Rebase.
>>> Add rev-by from John in patches 1-5, 7, 8.
>>> Remove BdrvDirtyBitmap typedef from dirty-bitmap.h in patch 4. [Max]
>>> Add assertion on bm->meta in patch 9. [John]
>>>
>>> Two major features are added to block dirty bitmap (and underlying HBitmap) in
>>> this series: meta bitmap and serialization, together with all other supportive
>>> patches.
>>>
>>> Both operations are common in dirty bitmap migration and persistence: they need
>>> to find whether and which part of the dirty bitmap in question has changed with
>>> meta dirty bitmap, and they need to write it to the target with serialization.
>>>
>>>
>>> Fam Zheng (13):
>>> backup: Use Bitmap to replace "s->bitmap"
>>> block: Include hbitmap.h in block.h
>>> typedefs: Add BdrvDirtyBitmap
>>> block: Move block dirty bitmap code to separate files
>>> block: Remove unused typedef of BlockDriverDirtyHandler
>>> block: Hide HBitmap in block dirty bitmap interface
>>> HBitmap: Introduce "meta" bitmap to track bit changes
>>> tests: Add test code for meta bitmap
>>> block: Support meta dirty bitmap
>>> block: Add two dirty bitmap getters
>>> block: Assert that bdrv_release_dirty_bitmap succeeded
>>> tests: Add test code for hbitmap serialization
>>> block: More operations for meta dirty bitmap
>>>
>>> Vladimir Sementsov-Ogievskiy (2):
>>> hbitmap: serialization
>>> block: BdrvDirtyBitmap serialization interface
>>>
>>> block.c | 360 -----------------------------
>>> block/Makefile.objs | 2 +-
>>> block/backup.c | 25 +-
>>> block/dirty-bitmap.c | 535 +++++++++++++++++++++++++++++++++++++++++++
>>> block/mirror.c | 15 +-
>>> include/block/block.h | 40 +---
>>> include/block/dirty-bitmap.h | 75 ++++++
>>> include/qemu/hbitmap.h | 96 ++++++++
>>> include/qemu/typedefs.h | 2 +
>>> tests/test-hbitmap.c | 255 +++++++++++++++++++++
>>> util/hbitmap.c | 203 ++++++++++++++--
>>> 11 files changed, 1177 insertions(+), 431 deletions(-)
>>> create mode 100644 block/dirty-bitmap.c
>>> create mode 100644 include/block/dirty-bitmap.h
>>>
>>
>> --
>> Best regards,
>> Vladimir
>>
>>
--
Best regards,
Vladimir
next prev parent reply other threads:[~2016-06-02 11:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 4:44 [Qemu-devel] [PATCH v4 00/15] Dirty bitmap changes for migration/persistence work Fam Zheng
2016-03-08 4:44 ` [Qemu-devel] [PATCH v4 01/15] backup: Use Bitmap to replace "s->bitmap" Fam Zheng
2016-03-08 4:44 ` [Qemu-devel] [PATCH v4 02/15] block: Include hbitmap.h in block.h Fam Zheng
2016-03-08 4:44 ` [Qemu-devel] [PATCH v4 03/15] typedefs: Add BdrvDirtyBitmap Fam Zheng
2016-03-08 4:44 ` [Qemu-devel] [PATCH v4 04/15] block: Move block dirty bitmap code to separate files Fam Zheng
2016-03-08 4:44 ` [Qemu-devel] [PATCH v4 05/15] block: Remove unused typedef of BlockDriverDirtyHandler Fam Zheng
2016-03-08 4:44 ` [Qemu-devel] [PATCH v4 06/15] block: Hide HBitmap in block dirty bitmap interface Fam Zheng
2016-03-11 13:54 ` Max Reitz
2016-03-11 14:27 ` Max Reitz
2016-03-08 4:44 ` [Qemu-devel] [PATCH v4 07/15] HBitmap: Introduce "meta" bitmap to track bit changes Fam Zheng
2016-03-11 14:48 ` Max Reitz
2016-03-08 4:44 ` [Qemu-devel] [PATCH v4 08/15] tests: Add test code for meta bitmap Fam Zheng
2016-03-11 14:58 ` Max Reitz
2016-06-03 2:38 ` Fam Zheng
2016-03-08 4:45 ` [Qemu-devel] [PATCH v4 09/15] block: Support meta dirty bitmap Fam Zheng
2016-03-11 15:17 ` Max Reitz
2016-06-03 2:42 ` Fam Zheng
2016-03-08 4:45 ` [Qemu-devel] [PATCH v4 10/15] block: Add two dirty bitmap getters Fam Zheng
2016-03-08 4:45 ` [Qemu-devel] [PATCH v4 11/15] block: Assert that bdrv_release_dirty_bitmap succeeded Fam Zheng
2016-03-11 15:25 ` Max Reitz
2016-03-08 4:45 ` [Qemu-devel] [PATCH v4 12/15] hbitmap: serialization Fam Zheng
2016-03-11 16:27 ` Max Reitz
2016-03-14 11:58 ` Vladimir Sementsov-Ogievskiy
2016-03-08 4:45 ` [Qemu-devel] [PATCH v4 13/15] block: BdrvDirtyBitmap serialization interface Fam Zheng
2016-03-08 4:45 ` [Qemu-devel] [PATCH v4 14/15] tests: Add test code for hbitmap serialization Fam Zheng
2016-03-08 4:45 ` [Qemu-devel] [PATCH v4 15/15] block: More operations for meta dirty bitmap Fam Zheng
2016-03-11 16:32 ` Max Reitz
2016-03-11 13:57 ` [Qemu-devel] [PATCH v4 00/15] Dirty bitmap changes for migration/persistence work Max Reitz
2016-03-11 19:30 ` John Snow
2016-05-25 14:45 ` Vladimir Sementsov-Ogievskiy
2016-05-26 0:47 ` Fam Zheng
2016-06-02 11:43 ` Vladimir Sementsov-Ogievskiy [this message]
2016-06-02 22:49 ` John Snow
2016-06-03 2:22 ` Fam Zheng
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=57501BCF.203@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=famz@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).