All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org, mreitz@redhat.com, pbonzini@redhat.com,
	jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/4] Bitmap clean-up patches for 2.6
Date: Thu, 26 Nov 2015 14:15:08 +0800	[thread overview]
Message-ID: <20151126061508.GH14630@ad.usersys.redhat.com> (raw)
In-Reply-To: <56555BEB.8080105@virtuozzo.com>

On Wed, 11/25 09:57, Vladimir Sementsov-Ogievskiy wrote:
> Hmm, stop. Very bad thing (sorry, that I didn't realize it before):
> 
> This breaks my dirty bitmap migration series with its meta bitmaps.
> Meta bitmap is an additional HBitmap in BdrvDirtyBitmap, which
> tracks dirtiness of this BdrvDirtyBitmap. And it (meta bitmap) have
> its own granularity of course. Or we will have to maintain
> additional meta_gran_shift and lots of duplicated code..
> 
> If we speak about splitting granularity out of HBitmap, then the
> most true way should be
> 
> struct HBitmapGranuled {
>   struct HBitmap *hb;
>   uint32_t gran_shift;
> }
> 
> with all supporting functions and iterators.

Then it's not worth making this change, let's drop patch 3 & 4 for now.

Fam

      reply	other threads:[~2015-11-26  6:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25  4:19 [Qemu-devel] [PATCH v3 0/4] Bitmap clean-up patches for 2.6 Fam Zheng
2015-11-25  4:19 ` [Qemu-devel] [PATCH v3 1/4] backup: Use Bitmap to replace "s->bitmap" Fam Zheng
2015-11-25  4:19 ` [Qemu-devel] [PATCH v3 2/4] block: Hide HBitmap in block dirty bitmap interface Fam Zheng
2015-11-25  4:19 ` [Qemu-devel] [PATCH v3 3/4] block: Manage granularity in BdrvDirtyBitmap Fam Zheng
2015-11-25  4:19 ` [Qemu-devel] [PATCH v3 4/4] hbitmap: Drop "granularity" Fam Zheng
2015-11-25  6:57 ` [Qemu-devel] [PATCH v3 0/4] Bitmap clean-up patches for 2.6 Vladimir Sementsov-Ogievskiy
2015-11-26  6:15   ` 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=20151126061508.GH14630@ad.usersys.redhat.com \
    --to=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.