From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
pbonzini@redhat.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC for-2.6 1/3] HBitmap: Introduce "meta" bitmap to track bit changes
Date: Wed, 9 Dec 2015 14:51:41 +0300 [thread overview]
Message-ID: <566815CD.8000509@virtuozzo.com> (raw)
In-Reply-To: <20151208013102.GB7567@ad.usersys.redhat.com>
On 08.12.2015 04:31, Fam Zheng wrote:
> On Mon, 12/07 16:32, Vladimir Sementsov-Ogievskiy wrote:
>> On 07.12.2015 08:59, Fam Zheng wrote:
>>> The meta bitmap will have the same size and granularity as the tracked
>>> bitmap, and upon each bit toggle, the corresponding bit in the meta
>>> bitmap, at an identical position, will be set.
>> No, meta bitmap should not have same granularity. If we have 16tb
>> storage, then 16kb granulated bitmap will occupy more then 128 mb.
>> And additional meta bitmap of the same size and granularity is
>> redundant 128+ mb of RAM, when actually we need meta bitmap for
>> blocks for example of 1mb and it should occupy about 128 bits.
> Makes sense, do you prefer a parameterized granularity, or a fixed scaling like
> one bit for 1 word?
Parametrized is better I thing. We will be able easily change it. Also
as John writes it may be that it should be different for
persistance/migration..
>
> Fam
>
>>
>>> Signed-off-by: Fam Zheng <famz@redhat.com>
>>> ---
>>> include/qemu/hbitmap.h | 7 +++++++
>>> util/hbitmap.c | 22 ++++++++++++++++++++++
>>> 2 files changed, 29 insertions(+)
>>>
>>> diff --git a/include/qemu/hbitmap.h b/include/qemu/hbitmap.h
>>> index bb94a00..09a6b06 100644
>>> --- a/include/qemu/hbitmap.h
>>> +++ b/include/qemu/hbitmap.h
>>> @@ -181,6 +181,13 @@ void hbitmap_iter_init(HBitmapIter *hbi, const HBitmap *hb, uint64_t first);
>>> */
>>> unsigned long hbitmap_iter_skip_words(HBitmapIter *hbi);
>>> +/* hbitmap_create_meta
>>> + * @hb: The HBitmap to operate on.
>>> + *
>>> + * Create a "meta" hbitmap to track dirtiness of the bits in this HBitmap.
>>> + */
>>> +HBitmap *hbitmap_create_meta(HBitmap *hb);
>>> +
>>> /**
>>> * hbitmap_iter_next:
>>> * @hbi: HBitmapIter to operate on.
>>> diff --git a/util/hbitmap.c b/util/hbitmap.c
>>> index 50b888f..3ad406e 100644
>>> --- a/util/hbitmap.c
>>> +++ b/util/hbitmap.c
>>> @@ -81,6 +81,9 @@ struct HBitmap {
>>> */
>>> int granularity;
>>> + /* A meta dirty bitmap to track the dirtiness of bits in this HBitmap. */
>>> + HBitmap *meta;
>>> +
>>> /* A number of progressively less coarse bitmaps (i.e. level 0 is the
>>> * coarsest). Each bit in level N represents a word in level N+1 that
>>> * has a set bit, except the last level where each bit represents the
>>> @@ -232,6 +235,7 @@ static inline bool hb_set_elem(unsigned long *elem, uint64_t start, uint64_t las
>>> /* The recursive workhorse (the depth is limited to HBITMAP_LEVELS)... */
>>> static void hb_set_between(HBitmap *hb, int level, uint64_t start, uint64_t last)
>>> {
>>> + uint64_t save_start = start;
>>> size_t pos = start >> BITS_PER_LEVEL;
>>> size_t lastpos = last >> BITS_PER_LEVEL;
>>> bool changed = false;
>>> @@ -252,6 +256,9 @@ static void hb_set_between(HBitmap *hb, int level, uint64_t start, uint64_t last
>>> }
>>> }
>>> changed |= hb_set_elem(&hb->levels[level][i], start, last);
>>> + if (hb->meta && level == HBITMAP_LEVELS - 1 && changed) {
>>> + hbitmap_set(hb->meta, save_start, last - save_start + 1);
>>> + }
>>> /* If there was any change in this layer, we may have to update
>>> * the one above.
>>> @@ -298,6 +305,7 @@ static inline bool hb_reset_elem(unsigned long *elem, uint64_t start, uint64_t l
>>> /* The recursive workhorse (the depth is limited to HBITMAP_LEVELS)... */
>>> static void hb_reset_between(HBitmap *hb, int level, uint64_t start, uint64_t last)
>>> {
>>> + uint64_t save_start = start;
>>> size_t pos = start >> BITS_PER_LEVEL;
>>> size_t lastpos = last >> BITS_PER_LEVEL;
>>> bool changed = false;
>>> @@ -336,6 +344,10 @@ static void hb_reset_between(HBitmap *hb, int level, uint64_t start, uint64_t la
>>> lastpos--;
>>> }
>>> + if (hb->meta && level == HBITMAP_LEVELS - 1 && changed) {
>>> + hbitmap_set(hb->meta, save_start, last - save_start + 1);
>>> + }
>>> +
>>> if (level > 0 && changed) {
>>> hb_reset_between(hb, level - 1, pos, lastpos);
>>> }
>>> @@ -384,6 +396,9 @@ void hbitmap_free(HBitmap *hb)
>>> for (i = HBITMAP_LEVELS; i-- > 0; ) {
>>> g_free(hb->levels[i]);
>>> }
>>> + if (hb->meta) {
>>> + hbitmap_free(hb->meta);
>>> + }
>>> g_free(hb);
>>> }
>>> @@ -493,3 +508,10 @@ bool hbitmap_merge(HBitmap *a, const HBitmap *b)
>>> return true;
>>> }
>>> +
>>> +HBitmap *hbitmap_create_meta(HBitmap *hb)
>>> +{
>>> + assert(!hb->meta);
>>> + hb->meta = hbitmap_alloc(hb->size, hb->granularity);
>>> + return hb->meta;
>>> +}
>>
>> --
>> Best regards,
>> Vladimir
>> * now, @virtuozzo.com instead of @parallels.com. Sorry for this inconvenience.
>>
--
Best regards,
Vladimir
* now, @virtuozzo.com instead of @parallels.com. Sorry for this inconvenience.
next prev parent reply other threads:[~2015-12-09 11:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 5:59 [Qemu-devel] [PATCH RFC for-2.6 0/3] block: Add meta dirty bitmap for migration/persistence Fam Zheng
2015-12-07 5:59 ` [Qemu-devel] [PATCH RFC for-2.6 1/3] HBitmap: Introduce "meta" bitmap to track bit changes Fam Zheng
2015-12-07 13:32 ` Vladimir Sementsov-Ogievskiy
2015-12-08 1:31 ` Fam Zheng
2015-12-09 11:51 ` Vladimir Sementsov-Ogievskiy [this message]
2015-12-30 10:53 ` Vladimir Sementsov-Ogievskiy
2015-12-30 11:07 ` Fam Zheng
2015-12-30 11:26 ` Vladimir Sementsov-Ogievskiy
2016-01-21 10:58 ` Vladimir Sementsov-Ogievskiy
2016-01-22 3:10 ` Fam Zheng
2015-12-07 5:59 ` [Qemu-devel] [PATCH RFC for-2.6 2/3] tests: Add test code for meta bitmap Fam Zheng
2015-12-07 5:59 ` [Qemu-devel] [PATCH RFC for-2.6 3/3] block: Support meta dirty bitmap Fam Zheng
2015-12-07 14:19 ` [Qemu-devel] [PATCH RFC for-2.6 0/3] block: Add meta dirty bitmap for migration/persistence Vladimir Sementsov-Ogievskiy
2015-12-08 1:42 ` Fam Zheng
2015-12-09 11:46 ` Vladimir Sementsov-Ogievskiy
2015-12-07 23:47 ` John Snow
2015-12-08 1:36 ` Fam Zheng
2015-12-09 11:57 ` 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=566815CD.8000509@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).