All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	pbonzini@redhat.com, armbru@redhat.com, eblake@redhat.com,
	famz@redhat.com, stefanha@redhat.com, amit.shah@redhat.com,
	mreitz@redhat.com, kwolf@redhat.com, peter.maydell@linaro.org,
	dgilbert@redhat.com, den@openvz.org, jsnow@redhat.com,
	lirans@il.ibm.com
Subject: Re: [Qemu-devel] [PATCH 12/18] migration: add postcopy migration of dirty bitmaps
Date: Fri, 04 Nov 2016 14:09:21 +0100	[thread overview]
Message-ID: <87h97no0hq.fsf@emacs.mitica> (raw)
In-Reply-To: <1471343175-14945-13-git-send-email-vsementsov@virtuozzo.com> (Vladimir Sementsov-Ogievskiy's message of "Tue, 16 Aug 2016 13:26:09 +0300")

Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> wrote:
> Postcopy migration of dirty bitmaps. Only named dirty bitmaps,
> associated with root nodes and non-root named nodes are migrated.
>
> If destination qemu is already containing a dirty bitmap with the same name
> as a migrated bitmap (for the same node), than, if their granularities are
> the same the migration will be done, otherwise the error will be generated.
>
> If destination qemu doesn't contain such bitmap it will be created.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>

> diff --git a/migration/block-dirty-bitmap.c b/migration/block-dirty-bitmap.c
> new file mode 100644
> index 0000000..c668d02
> --- /dev/null
> +++ b/migration/block-dirty-bitmap.c
> @@ -0,0 +1,699 @@
> +/*
> + * QEMU dirty bitmap migration
> + *
> + * Postcopy migration of dirty bitmaps. Only named dirty bitmaps, associated
> + * with root nodes and non-root named nodes are migrated.
> + *
> + * If destination qemu is already containing a dirty bitmap with the same name
> + * as a migrated bitmap (for the same node), than, if their granularities are
> + * the same the migration will be done, otherwise the error will be generated.
> + *
> + * If destination qemu doesn't contain such bitmap it will be created.
> + *
> + * format of migration:
> + *
> + * # Header (shared for different chunk types)
> + * 1, 2 or 4 bytes: flags (see qemu_{put,put}_flags)
> + * [ 1 byte: node name size ] \  flags & DEVICE_NAME
> + * [ n bytes: node name     ] /
> + * [ 1 byte: bitmap name size ] \  flags & BITMAP_NAME
> + * [ n bytes: bitmap name     ] /
> + *
> + * # Start of bitmap migration (flags & START)
> + * header
> + * be64: granularity
> + * 1 byte: bitmap enabled flag
> + *
> + * # Complete of bitmap migration (flags & COMPLETE)
> + * header
> + *
> + * # Data chunk of bitmap migration
> + * header
> + * be64: start sector
> + * be32: number of sectors
> + * [ be64: buffer size  ] \ ! (flags & ZEROES)
> + * [ n bytes: buffer    ] /
> + *
> + * The last chunk in stream should contain flags & EOS. The chunk may skip
> + * device and/or bitmap names, assuming them to be the same with the previous
> + * chunk.
> + *
> + *
> + * This file is derived from migration/block.c
> + *
> + * Author:
> + * Vladimir Sementsov-Ogievskiy <vsementsov@parallels.com>
> + *
> + * original copyright message:
> + * =====================================================================
> + * Copyright IBM, Corp. 2009
> + *
> + * Authors:
> + *  Liran Schour   <lirans@il.ibm.com>
> + *
> + * This work is licensed under the terms of the GNU GPL, version 2.  See
> + * the COPYING file in the top-level directory.
> + *
> + * Contributions after 2012-01-13 are licensed under the terms of the
> + * GNU GPL, version 2 or (at your option) any later version.
> + * =====================================================================
> + */

I think that the normal practice is putting first the copyright and then
the comment of the file.

> +static void qemu_put_bitmap_flags(QEMUFile *f, uint32_t flags)
> +{
> +    if (!(flags & 0xffffff00)) {
> +        qemu_put_byte(f, flags);
> +        return;
> +    }
> +
> +    if (!(flags & 0xffff0000)) {
> +        qemu_put_be16(f, flags | DIRTY_BITMAP_MIG_FLAGS_SIZE_16);
> +        return;
> +    }
> +
> +    qemu_put_be32(f, flags | DIRTY_BITMAP_MIG_FLAGS_SIZE_32);
> +}

Do need flags so many times to be a good idea to spend two flags and
make the code more complex?  Couldn't just sent always the 32bit word
and call it a day?

I have only looked at the stuff quickly from the migration point of
view, not about the bitmap stuff.

> +static void send_bitmap_complete(QEMUFile *f, DirtyBitmapMigBitmapState *dbms)
> +{
> +    send_bitmap_header(f, dbms, DIRTY_BITMAP_MIG_FLAG_COMPLETE);
> +}
> +
> +static void send_bitmap_bits(QEMUFile *f, DirtyBitmapMigBitmapState *dbms,
> +                             uint64_t start_sector, uint32_t nr_sectors)
> +{
> +    /* align for buffer_is_zero() */
> +    uint64_t align = 4 * sizeof(long);
> +    uint64_t unaligned_size =
> +        bdrv_dirty_bitmap_serialization_size(dbms->bitmap,
> +                                             start_sector, nr_sectors);
> +    uint64_t buf_size = (unaligned_size + align - 1) & ~(align - 1);
> +    uint8_t *buf = g_malloc0(buf_size);
> +    uint32_t flags = DIRTY_BITMAP_MIG_FLAG_BITS;
> +
> +    bdrv_dirty_bitmap_serialize_part(dbms->bitmap, buf,
> +                                     start_sector, nr_sectors);
> +
> +    if (buffer_is_zero(buf, buf_size)) {
> +        g_free(buf);
> +        buf = NULL;
> +        flags |= DIRTY_BITMAP_MIG_FLAG_ZEROES;
> +    }
> +
> +    DPRINTF("parameters:"
> +            "\n   flags:        %x"
> +            "\n   start_sector: %" PRIu64
> +            "\n   nr_sectors:   %" PRIu32
> +            "\n   data_size:    %" PRIu64 "\n",
> +            flags, start_sector, nr_sectors, buf_size);

Now we are adding traces, not DPRINF's to new code in general.
Same for all DPRINTFs

> +
> +    send_bitmap_header(f, dbms, flags);
> +
> +    qemu_put_be64(f, start_sector);
> +    qemu_put_be32(f, nr_sectors);
> +
> +    /* if a block is zero we need to flush here since the network
> +     * bandwidth is now a lot higher than the storage device bandwidth.
> +     * thus if we queue zero blocks we slow down the migration.
> +     * also, skip writing block when migrate only dirty bitmaps. */
> +    if (flags & DIRTY_BITMAP_MIG_FLAG_ZEROES) {
> +        qemu_fflush(f);

I thought that we were missing the g_free(buf) here, not sure if it is
better to put the return here, or do an else for the rest of the code.

  reply	other threads:[~2016-11-04 13:09 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 10:25 [Qemu-devel] [PATCH 00/18] Dirty bitmaps postcopy migration Vladimir Sementsov-Ogievskiy
2016-08-16 10:25 ` [Qemu-devel] [PATCH 01/18] migration: add has_postcopy savevm handler Vladimir Sementsov-Ogievskiy
2016-11-04 12:32   ` Juan Quintela
2016-08-16 10:25 ` [Qemu-devel] [PATCH 02/18] migration: fix ram_save_pending Vladimir Sementsov-Ogievskiy
2016-08-17 12:12   ` Dr. David Alan Gilbert
2016-11-04 12:32   ` Juan Quintela
2016-08-16 10:26 ` [Qemu-devel] [PATCH 03/18] migration: split common postcopy out of ram postcopy Vladimir Sementsov-Ogievskiy
2016-11-04 12:49   ` Juan Quintela
2016-08-16 10:26 ` [Qemu-devel] [PATCH 04/18] migration: introduce postcopy-only pending Vladimir Sementsov-Ogievskiy
2016-11-04 12:46   ` Juan Quintela
2016-11-21 11:05     ` Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 05/18] block: add bdrv_next_dirty_bitmap() Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 06/18] block: add bdrv_dirty_bitmap_enable_successor() Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 07/18] qapi: add dirty-bitmaps migration capability Vladimir Sementsov-Ogievskiy
2016-08-17  9:06   ` Fam Zheng
2016-08-16 10:26 ` [Qemu-devel] [PATCH 08/18] block/dirty-bitmap: add bdrv_dirty_bitmap_release_successor Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 09/18] migration: include migrate_dirty_bitmaps in migrate_postcopy Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 10/18] migration/qemu-file: add qemu_put_counted_string() Vladimir Sementsov-Ogievskiy
2016-08-17  9:09   ` Fam Zheng
2016-11-21  5:23     ` Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 11/18] migration: add is_active_iterate handler Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 12/18] migration: add postcopy migration of dirty bitmaps Vladimir Sementsov-Ogievskiy
2016-11-04 13:09   ` Juan Quintela [this message]
2016-11-21  6:35     ` Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 13/18] iotests: maintain several vms in test Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 14/18] iotests: add add_incoming_migration to VM class Vladimir Sementsov-Ogievskiy
2016-08-16 10:26 ` [Qemu-devel] [PATCH 15/18] qapi: add md5 checksum of last dirty bitmap level to query-block Vladimir Sementsov-Ogievskiy
2016-08-16 10:37   ` Daniel P. Berrange
2016-08-16 10:42     ` Daniel P. Berrange
2016-08-16 10:26 ` [Qemu-devel] [PATCH 16/18] iotests: add default node-name Vladimir Sementsov-Ogievskiy
2016-08-17  9:19   ` Fam Zheng
2016-08-16 10:26 ` [Qemu-devel] [PATCH 17/18] iotests: add dirty bitmap migration test 169 Vladimir Sementsov-Ogievskiy
2016-08-17 11:35   ` Fam Zheng
2016-08-16 10:26 ` [Qemu-devel] [PATCH 18/18] iotests: add dirty bitmap postcopy test Vladimir Sementsov-Ogievskiy
2016-08-17 11:47 ` [Qemu-devel] [PATCH 00/18] Dirty bitmaps postcopy migration Fam Zheng
2016-08-17 12:15   ` Vladimir Sementsov-Ogievskiy
2016-08-20 11:21     ` Fam Zheng
2016-08-17 12:35 ` Dr. David Alan Gilbert
2016-08-17 13:54   ` Vladimir Sementsov-Ogievskiy
2016-09-30 11:00 ` Vladimir Sementsov-Ogievskiy
2016-10-12 11:32 ` Vladimir Sementsov-Ogievskiy
2016-10-25 13:04 ` [Qemu-devel] ping " Vladimir Sementsov-Ogievskiy
2016-11-02 11:13   ` Stefan Hajnoczi
2016-11-02 12:05     ` Denis V. Lunev
2016-11-04 13:12       ` Juan Quintela
2016-11-04 13:27         ` Denis V. Lunev

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=87h97no0hq.fsf@emacs.mitica \
    --to=quintela@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=den@openvz.org \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lirans@il.ibm.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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.