From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v2 01/10] migration: Increase default number of multifd channels to 16
Date: Tue, 7 Jan 2020 13:42:05 +0000 [thread overview]
Message-ID: <20200107134205.GM3368802@redhat.com> (raw)
In-Reply-To: <87muazpf2v.fsf@trasno.org>
On Tue, Jan 07, 2020 at 02:32:24PM +0100, Juan Quintela wrote:
> Daniel P. Berrangé <berrange@redhat.com> wrote:
> >> - What does libvirt prefferes
> >
> > Libvirt doesn't really have an opinion in this case. I believe we'll
> > always set the number of channels on both src & dst, so we don't
> > see the defaults.
>
> What does libvirt does today for this value?
Libvirt doesn't have any default value. By default migration uses a
single connection. The mgmt app can request multiple connections
for the migration, which will cause libvirt to turn on multifd with
the request channel count.
Essentially we avoid the problem by not having a separate tunable
for "multifd enable" & "multifd channels" - we only have one tunable
"connection count". Thus the idea of enabling multifd with a default
channel count doesn't exist.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-01-07 14:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 2:01 [PATCH v2 00/10] Multifd Migration Compression Juan Quintela
2019-12-18 2:01 ` [PATCH v2 01/10] migration: Increase default number of multifd channels to 16 Juan Quintela
2020-01-03 16:51 ` Dr. David Alan Gilbert
2020-01-03 16:58 ` Daniel P. Berrangé
2020-01-03 17:01 ` Dr. David Alan Gilbert
2020-01-03 17:12 ` Daniel P. Berrangé
2020-01-03 17:32 ` Dr. David Alan Gilbert
2020-01-03 18:25 ` Juan Quintela
2020-01-07 12:49 ` Daniel P. Berrangé
2020-01-07 13:32 ` Juan Quintela
2020-01-07 13:42 ` Daniel P. Berrangé [this message]
2020-01-03 17:49 ` Daniel P. Berrangé
2019-12-18 2:01 ` [PATCH v2 02/10] migration-test: Add migration multifd test Juan Quintela
2019-12-18 2:01 ` [PATCH v2 03/10] migration-test: introduce functions to handle string parameters Juan Quintela
2020-01-03 16:57 ` Dr. David Alan Gilbert
2019-12-18 2:01 ` [PATCH v2 04/10] migration: Make multifd_save_setup() get an Error parameter Juan Quintela
2020-01-03 16:46 ` Dr. David Alan Gilbert
2020-01-07 12:35 ` Juan Quintela
2019-12-18 2:01 ` [PATCH v2 05/10] migration: Make multifd_load_setup() " Juan Quintela
2020-01-03 17:22 ` Dr. David Alan Gilbert
2020-01-07 13:00 ` Juan Quintela
2019-12-18 2:01 ` [PATCH v2 06/10] migration: Add multifd-compress parameter Juan Quintela
2019-12-19 7:41 ` Markus Armbruster
2020-01-03 17:57 ` Dr. David Alan Gilbert
2020-01-07 13:03 ` Juan Quintela
2019-12-18 2:01 ` [PATCH v2 07/10] migration: Make no compression operations into its own structure Juan Quintela
2020-01-03 18:20 ` Dr. David Alan Gilbert
2020-01-07 13:08 ` Juan Quintela
2019-12-18 2:01 ` [PATCH v2 08/10] migration: Add zlib compression multifd support Juan Quintela
2019-12-18 2:01 ` [PATCH v2 09/10] configure: Enable test and libs for zstd Juan Quintela
2019-12-18 2:01 ` [PATCH v2 10/10] migration: Add zstd compression multifd support Juan Quintela
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=20200107134205.GM3368802@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@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).