From: Juan Quintela <quintela@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Peter Xu" <peterx@redhat.com>,
qemu-devel@nongnu.org, "Fabiano Rosas" <farosas@suse.de>,
"Chensheng Dong" <chdong@redhat.com>,
"Zhiyi Guo" <zhguo@redhat.com>, "Eric Blake" <eblake@redhat.com>,
"Joao Martins" <joao.m.martins@oracle.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v4] migration: Allow user to specify available switchover bandwidth
Date: Thu, 19 Oct 2023 14:23:35 +0200 [thread overview]
Message-ID: <875y324x88.fsf@secure.mitica> (raw)
In-Reply-To: <87wmvkxvza.fsf@pond.sub.org> (Markus Armbruster's message of "Wed, 18 Oct 2023 08:53:13 +0200")
Markus Armbruster <armbru@redhat.com> wrote:
> Peter Xu <peterx@redhat.com> writes:
[..]
>>> "unconvergence" isn't a word :)
>>>
>>> Suggest "like migration not converging, because the automatically
>>> detected migration bandwidth is hilariously low for whatever reason."
>>>
>>> Appreciate the thorough explanation!
>>
>> Thanks for reviewing!
>>
>> The patch is already in today's migration pull, so unfortunately no planned
>> repost for now. I'll amend the commit message and collect the ACK if I'll
>> need to redo it.
>
> Didn't see the PR, and didn't expect it so soon.
Sorry.
When a series is at v4 reviewed I tend to be faster pulling.
For new series, I try to let them in the list for a couple of days to
let people comment.
Later, Juan.
prev parent reply other threads:[~2023-10-19 12:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 22:19 [PATCH v4] migration: Allow user to specify available switchover bandwidth Peter Xu
2023-10-11 12:58 ` Juan Quintela
2023-10-17 14:12 ` Markus Armbruster
2023-10-17 15:37 ` Peter Xu
2023-10-18 6:53 ` Markus Armbruster
2023-10-19 12:23 ` Juan Quintela [this message]
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=875y324x88.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=chdong@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=joao.m.martins@oracle.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).