qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 00/13] Dirty bitmap changes for migration/persistence work
Date: Fri, 8 Jan 2016 08:29:55 +0800	[thread overview]
Message-ID: <20160108002955.GA808@ad.usersys.redhat.com> (raw)
In-Reply-To: <568ED985.5050104@redhat.com>

On Thu, 01/07 16:32, John Snow wrote:
> 
> 
> On 01/04/2016 05:27 AM, Fam Zheng wrote:
> > 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 (11):
> >   backup: Use Bitmap to replace "s->bitmap"
> >   typedefs: Add BdrvDirtyBitmap and HBitmapIter
> >   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
> > 
> > Vladimir Sementsov-Ogievskiy (2):
> >   hbitmap: serialization
> >   block: BdrvDirtyBitmap serialization interface
> > 
> >  block.c                      | 339 -----------------------------
> >  block/Makefile.objs          |   2 +-
> >  block/backup.c               |  25 ++-
> >  block/dirty-bitmap.c         | 491 +++++++++++++++++++++++++++++++++++++++++++
> >  block/mirror.c               |  14 +-
> >  include/block/block.h        |  39 +---
> >  include/block/dirty-bitmap.h |  70 ++++++
> >  include/qemu/hbitmap.h       |  84 ++++++++
> >  include/qemu/typedefs.h      |   3 +
> >  tests/test-hbitmap.c         | 252 ++++++++++++++++++++++
> >  util/hbitmap.c               | 197 +++++++++++++++--
> >  11 files changed, 1106 insertions(+), 410 deletions(-)
> >  create mode 100644 block/dirty-bitmap.c
> >  create mode 100644 include/block/dirty-bitmap.h
> > 
> 
> That's all I've got for now. Happy New Year!
> 
> What's your roadmap for these patches? This, then QBM?

Yes, QBM is on the way, right after this.

Fam

      reply	other threads:[~2016-01-08  0:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 10:27 [Qemu-devel] [PATCH 00/13] Dirty bitmap changes for migration/persistence work Fam Zheng
2016-01-04 10:27 ` [Qemu-devel] [PATCH 01/13] backup: Use Bitmap to replace "s->bitmap" Fam Zheng
2016-01-04 10:27 ` [Qemu-devel] [PATCH 02/13] typedefs: Add BdrvDirtyBitmap and HBitmapIter Fam Zheng
2016-01-05 22:14   ` John Snow
2016-01-08  2:13     ` Fam Zheng
2016-01-04 10:27 ` [Qemu-devel] [PATCH 03/13] block: Move block dirty bitmap code to separate files Fam Zheng
2016-01-05 22:32   ` John Snow
2016-01-04 10:27 ` [Qemu-devel] [PATCH 04/13] block: Remove unused typedef of BlockDriverDirtyHandler Fam Zheng
2016-01-05 22:35   ` John Snow
2016-01-04 10:27 ` [Qemu-devel] [PATCH 05/13] block: Hide HBitmap in block dirty bitmap interface Fam Zheng
2016-01-05 23:01   ` John Snow
2016-01-20  5:09     ` Fam Zheng
2016-01-04 10:27 ` [Qemu-devel] [PATCH 06/13] HBitmap: Introduce "meta" bitmap to track bit changes Fam Zheng
2016-01-06  0:09   ` John Snow
2016-01-11 15:40   ` Vladimir Sementsov-Ogievskiy
2016-01-11 18:56     ` John Snow
2016-01-12  8:25       ` Vladimir Sementsov-Ogievskiy
2016-01-04 10:27 ` [Qemu-devel] [PATCH 07/13] tests: Add test code for meta bitmap Fam Zheng
2016-01-06 20:46   ` John Snow
2016-01-04 10:27 ` [Qemu-devel] [PATCH 08/13] block: Support meta dirty bitmap Fam Zheng
2016-01-07 19:30   ` John Snow
2016-01-20  6:07     ` Fam Zheng
2016-01-20 21:46       ` John Snow
2016-01-04 10:27 ` [Qemu-devel] [PATCH 09/13] block: Add two dirty bitmap getters Fam Zheng
2016-01-07 19:35   ` John Snow
2016-01-04 10:27 ` [Qemu-devel] [PATCH 10/13] block: Assert that bdrv_release_dirty_bitmap succeeded Fam Zheng
2016-01-07 19:38   ` John Snow
2016-01-04 10:27 ` [Qemu-devel] [PATCH 11/13] hbitmap: serialization Fam Zheng
2016-01-07 21:11   ` John Snow
2016-01-11 15:12     ` Vladimir Sementsov-Ogievskiy
2016-01-11 14:48   ` Vladimir Sementsov-Ogievskiy
2016-01-11 15:19   ` Vladimir Sementsov-Ogievskiy
2016-01-04 10:27 ` [Qemu-devel] [PATCH 12/13] block: BdrvDirtyBitmap serialization interface Fam Zheng
2016-01-04 10:27 ` [Qemu-devel] [PATCH 13/13] tests: Add test code for hbitmap serialization Fam Zheng
2016-01-07 21:32 ` [Qemu-devel] [PATCH 00/13] Dirty bitmap changes for migration/persistence work John Snow
2016-01-08  0:29   ` Fam Zheng [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=20160108002955.GA808@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.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).