From: Het Gala <het.gala@nutanix.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com, dgilbert@redhat.com,
pbonzini@redhat.com, armbru@redhat.com, eblake@redhat.com,
prerna.saxena@nutanix.com,
Manish Mishra <manish.mishra@nutanix.com>
Subject: Re: [PATCH v2 3/7] multifd: adding multi-interface support for multifd on destination side
Date: Thu, 28 Jul 2022 20:35:09 +0530 [thread overview]
Message-ID: <c388063a-ea01-ca07-8e55-06556def7e82@nutanix.com> (raw)
In-Reply-To: <Yt/N629r3EpOLrHG@redhat.com>
On 26/07/22 4:50 pm, Daniel P. Berrangé wrote:
> On Thu, Jul 21, 2022 at 07:56:16PM +0000, Het Gala wrote:
>> i) Modified the format of qemu monitor command: 'migrate-incoming' by adding
>> a list, each element in the list to open socket listeners with a given
>> number of multifd channels.
>>
>> ii) Qemu starts with -incoming flag defer and -multi-fd-incoming defer to
>> allow the modified 'migrate-incoming' command to be used.
>>
>> iii) Format for -multi-fd-incoming flag as a comma separated string has been
>> added with each substring containing listener socket address and number
>> of sockets to open.
>>
>> Suggested-by: Manish Mishra <manish.mishra@nutanix.com>
>> Signed-off-by: Het Gala <het.gala@nutanix.com>
>
>> diff --git a/qemu-options.hx b/qemu-options.hx
>> index 79e00916a1..5555f0d2fd 100644
>> --- a/qemu-options.hx
>> +++ b/qemu-options.hx
>> @@ -4479,6 +4479,24 @@ SRST
>> to issuing the migrate\_incoming to allow the migration to begin.
>> ERST
>>
>> +DEF("multi-fd-incoming", HAS_ARG, QEMU_OPTION_multi_fd_incoming, \
>> + "-multi-fd-incoming tcp:[host]:port[:channel][,to=maxport][,ipv4=on|off][,ipv6=on|off]\n" \
>> + "-multi-fd-incoming defer\n" \
>> + " wait for the URI to be specified via\n" \
>> + " multi_fd_migrate_incoming\n",
>> + QEMU_ARCH_ALL)
>> +SRST
>> +``-multi-fd-incoming tcp:[host]:port[:channel][,to=maxport][,ipv4=on|off][,ipv6=on|off]``
>> + Prepare for multi-fd incoming migration, with multi-fd listening sockets
>> + on that connection. Default number of multi-fd channels is 2.
>> +
>> +``-multi-fd-incoming defer``
>> + Wait for the URI to be specified via multi_fd_migrate\_incoming. The
>> + monitor can be used to change settings (such as migration parameters)
>> + prior to issuing the multi_fd_migrate\_incoming to allow the migration
>> + to begin.
>> +ERST
> We should not be adding any new -multi-fd-incoming CLI parameter at all.
> The CLI is so unsuitable for any complex configuration param and this
> is a prime example.
>
> If anything we should fully deprecate anything that is not '-incoming defer'
> such that we become 100% QMP/QAPI based for incoming migration config.
> Sure Daniel. We will depricate this -multi-fd-incoming defer flag and
only keep QMP/QAPI based migration config in the coming patchset series.
> With regards,
> Daniel
With Regards,
Het Gala
next prev parent reply other threads:[~2022-07-28 15:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 19:56 [PATCH v2 0/7] multifd: Multiple interface support on top of Multifd Het Gala
2022-07-21 19:56 ` [PATCH v2 1/7] multifd: adding more helper functions in util files for live migration Het Gala
2022-07-21 19:56 ` [PATCH v2 2/7] multifd: modifying 'migrate' qmp command to add multifd socket on particular src and dest pair Het Gala
2022-07-26 11:13 ` Daniel P. Berrangé
2022-07-28 15:02 ` Het Gala
2022-08-02 7:53 ` Markus Armbruster
2022-08-08 6:11 ` Het Gala
2022-08-08 9:29 ` Daniel P. Berrangé
2022-08-29 4:34 ` Het Gala
2022-09-21 10:08 ` Het Gala
2022-11-21 12:26 ` Juan Quintela
2022-11-22 9:26 ` Daniel P. Berrangé
2022-08-08 9:29 ` Daniel P. Berrangé
2022-07-21 19:56 ` [PATCH v2 3/7] multifd: adding multi-interface support for multifd on destination side Het Gala
2022-07-26 11:20 ` Daniel P. Berrangé
2022-07-28 15:05 ` Het Gala [this message]
2022-07-21 19:56 ` [PATCH v2 4/7] multifd: HMP changes for multifd source and " Het Gala
2022-07-21 19:56 ` [PATCH v2 5/7] multifd: establishing connection between any non-default src and dest pair Het Gala
2022-07-26 10:44 ` Daniel P. Berrangé
2022-07-28 15:15 ` Het Gala
2022-07-21 19:56 ` [PATCH v2 6/7] muitlfd: Correcting nit : whitespace error changes in qemu-sockets.c file Het Gala
2022-07-21 19:56 ` [PATCH v2 7/7] multifd: adding support for multifd connections dynamically Het Gala
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=c388063a-ea01-ca07-8e55-06556def7e82@nutanix.com \
--to=het.gala@nutanix.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=manish.mishra@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=prerna.saxena@nutanix.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).