From: Eric Blake <eblake@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
qemu-devel@nongnu.org, jasowang@redhat.com, armbru@redhat.com,
laine@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/4] net/announce: Allow optional list of interfaces
Date: Mon, 10 Jun 2019 14:47:27 -0500 [thread overview]
Message-ID: <272867fd-1a3a-3cc2-9774-0feb694cd773@redhat.com> (raw)
In-Reply-To: <20190610184402.7090-2-dgilbert@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2057 bytes --]
On 6/10/19 1:43 PM, Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> Allow the caller to restrict the set of interfaces that announces are
> sent on. The default is still to send on all interfaces.
>
> e.g.
>
> { "execute": "announce-self", "arguments": { "initial": 50, "max": 550, "rounds": 5, "step": 50, "interfaces": ["vn2","vn1"] } }
>
> This doesn't affect the behaviour of migraiton announcments.
>
> Note: There's still only one timer for the qmp command, so that
> performing an 'announce-self' on one list of interfaces followed
> by another 'announce-self' on another list will stop the announces
> on the existing set.
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> +++ b/qapi/net.json
> @@ -699,6 +699,9 @@
> #
> # @step: Delay increase (in ms) after each self-announcement attempt
> #
> +# @interfaces: An optional list of interface names, which restrict the
restricts
> +# announcment to the listed interfaces. (Since 4.1)
announcement
> +#
> # Since: 4.0
> ##
>
> @@ -706,7 +709,8 @@
> 'data': { 'initial': 'int',
> 'max': 'int',
> 'rounds': 'int',
> - 'step': 'int' } }
> + 'step': 'int',
> + '*interfaces': ['str'] } }
>
> ##
> # @announce-self:
> @@ -718,9 +722,10 @@
> #
> # Example:
> #
> -# -> { "execute": "announce-self"
> +# -> { "execute": "announce-self",
Embarrassing that we didn't notice that one earlier.
> # "arguments": {
> -# "initial": 50, "max": 550, "rounds": 10, "step": 50 } }
> +# "initial": 50, "max": 550, "rounds": 10, "step": 50,
> +# "interfaces": ["vn2","vn3"] } }
Worth a space after the comma? Not required, but I think it looks nicer.
As I only focused on doc issues, I'll leave the full review to others.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-10 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 18:43 [Qemu-devel] [PATCH v3 0/4] network announce; interface selection & IDs Dr. David Alan Gilbert (git)
2019-06-10 18:43 ` [Qemu-devel] [PATCH v3 1/4] net/announce: Allow optional list of interfaces Dr. David Alan Gilbert (git)
2019-06-10 19:47 ` Eric Blake [this message]
2019-06-11 10:36 ` Dr. David Alan Gilbert
2019-06-10 18:44 ` [Qemu-devel] [PATCH v3 2/4] net/announce: Add HMP optional interface list Dr. David Alan Gilbert (git)
2019-06-10 18:44 ` [Qemu-devel] [PATCH v3 3/4] net/announce: Add optional ID Dr. David Alan Gilbert (git)
2019-06-10 19:53 ` Eric Blake
2019-06-12 15:32 ` Dr. David Alan Gilbert
2019-06-10 18:44 ` [Qemu-devel] [PATCH v3 4/4] net/announce: Add HMP " Dr. David Alan Gilbert (git)
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=272867fd-1a3a-3cc2-9774-0feb694cd773@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=laine@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).