From: Eric Blake <eblake@redhat.com>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: lvivier@redhat.com, dgilbert@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PULL 07/16] migration: Create x-multifd-page-count parameter
Date: Wed, 20 Sep 2017 08:59:49 -0500 [thread overview]
Message-ID: <52df88ba-6844-3569-2913-fa692a2ca6d6@redhat.com> (raw)
In-Reply-To: <20170920104639.2335-8-quintela@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On 09/20/2017 05:46 AM, Juan Quintela wrote:
> Indicates how many pages we are going to send in each batch to a multifd
> thread.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Reviewed-by: Peter Xu <peterx@redhat.com>
>
> +++ b/qapi/migration.json
> @@ -471,6 +471,9 @@
> # number of sockets used for migration. The
> # default value is 2 (since 2.11)
> #
> +# @x-multifd-page-count: Number of pages sent together to a thread
> +# The default value is 16 (since 2.11)
You're missing a '.' between sentences; it's more obvious when you no
longer have a newline between them when things are rendered to other
documentation formats.
Can be fixed as a followup.
> @@ -539,6 +542,9 @@
> # number of sockets used for migration. The
> # default value is 2 (since 2.11)
> #
> +# @x-multifd-page-count: Number of pages sent together to a thread
> +# The default value is 16 (since 2.11)
> +#
Multiple instances of it.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-09-20 14:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 10:46 [Qemu-devel] [PULL 00/16] Migration PULL request Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 01/16] migration: Create migration_ioc_process_incoming() Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 02/16] migration: Teach it about G_SOURCE_REMOVE Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 03/16] migration: Add comments to channel functions Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 04/16] migration: Create migration_has_all_channels Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 05/16] migration: Add multifd capability Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 06/16] migration: Create x-multifd-channels parameter Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 07/16] migration: Create x-multifd-page-count parameter Juan Quintela
2017-09-20 13:59 ` Eric Blake [this message]
2017-09-20 10:46 ` [Qemu-devel] [PULL 08/16] migration: Create multifd migration threads Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 09/16] migration: Split migration_fd_process_incoming Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 10/16] bitmap: remove BITOP_WORD() Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 11/16] bitmap: introduce bitmap_count_one() Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 12/16] bitmap: provide to_le/from_le helpers Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 13/16] migration: pass MigrationIncomingState* into migration check functions Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 14/16] migration: fix hardcoded function name in error report Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 15/16] migration: split ufd_version_check onto receive/request features part Juan Quintela
2017-09-20 10:46 ` [Qemu-devel] [PULL 16/16] migration: introduce postcopy-blocktime capability Juan Quintela
2017-09-20 11:42 ` [Qemu-devel] [PULL 00/16] Migration PULL request Juan Quintela
2017-09-20 19:32 ` Peter Maydell
2017-09-21 4:10 ` Peter Xu
2017-09-21 4:21 ` Peter Xu
2017-09-20 14:55 ` no-reply
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=52df88ba-6844-3569-2913-fa692a2ca6d6@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).