From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org,
Leonardo Bras Soares Passos <lsoaresp@redhat.com>,
Eric Blake <eblake@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Chensheng Dong <chdong@redhat.com>, Zhiyi Guo <zhguo@redhat.com>,
Fabiano Rosas <farosas@suse.de>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH] migration: Allow user to specify migration available bandwidth
Date: Tue, 25 Jul 2023 18:10:18 +0100 [thread overview]
Message-ID: <ZMAB+tI9kIid0kBI@redhat.com> (raw)
In-Reply-To: <ZL/6f7nNLw+iVHYL@x1n>
On Tue, Jul 25, 2023 at 12:38:23PM -0400, Peter Xu wrote:
> I see you used "convergance" explicitly even after PeterM's reply, is that
> what you prefer over "convergence"? I do see more occurances of
> "convergence" as a word in migration context, though.
Ignore my speling erors :-)
> Any better name you
> can come up with, before I just go with "max-convergence-bandwidth" (I
> really cannot come up with anything better than this or available-bandwidth
> for now)?
Anothre idea could be 'max-switchover-bandwidth' ?
With 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:[~2023-07-25 17:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 17:07 [PATCH] migration: Allow user to specify migration available bandwidth Peter Xu
2023-07-24 18:04 ` Daniel P. Berrangé
2023-07-24 18:12 ` Peter Maydell
2023-07-24 19:47 ` Peter Xu
2023-07-25 9:16 ` Daniel P. Berrangé
2023-07-25 15:54 ` Peter Xu
2023-07-25 16:09 ` Daniel P. Berrangé
2023-07-25 16:38 ` Peter Xu
2023-07-25 17:10 ` Daniel P. Berrangé [this message]
2023-07-26 15:19 ` Peter Xu
2023-07-25 11:10 ` Markus Armbruster
2023-07-25 16:42 ` Peter Xu
2023-07-26 6:21 ` Markus Armbruster
2023-07-26 15:12 ` Peter Xu
2023-08-04 12:06 ` Markus Armbruster
2023-08-04 13:28 ` Peter Xu
2023-08-05 8:13 ` Markus Armbruster
2023-08-04 13:39 ` Daniel P. Berrangé
2023-08-04 14:02 ` Peter Xu
2023-08-05 8:05 ` Markus Armbruster
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=ZMAB+tI9kIid0kBI@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=chdong@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=lsoaresp@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=zhguo@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 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.