From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, "Juan Quintela" <quintela@redhat.com>,
"Chensheng Dong" <chdong@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Joao Martins" <joao.m.martins@oracle.com>,
"Fabiano Rosas" <farosas@suse.de>, "Zhiyi Guo" <zhguo@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
lei4.wang@intel.com
Subject: [PATCH v3 0/1] migration: Add avail-switchover-bandwidth parameter
Date: Tue, 5 Sep 2023 15:38:01 -0400 [thread overview]
Message-ID: <20230905193802.250440-1-peterx@redhat.com> (raw)
This single-patch series is based on:
[PATCH v3 0/4] qapi/migration: Dedup migration parameter objects and fix tls-authz crash
Based-on: <20230905162335.235619-1-peterx@redhat.com>
I still added a cover letter to make sure the "Based-on" will be parsed all
right for e.g. patchew.
v3:
- Rebased to above patchset, dropped the 1st patch
- Renamed the parameter from "max-switchover-bandwidth" to
"avail-switchover-bandwidth"
- Fixed calculation [Joao]
For more information on the new parameter and why we need it, please read
commit message in the patch.
Please have a look, thanks.
Peter Xu (1):
migration: Allow user to specify available switchover bandwidth
qapi/migration.json | 11 +++++++++++
migration/migration.h | 2 +-
migration/options.h | 2 ++
migration/migration-hmp-cmds.c | 14 ++++++++++++++
migration/migration.c | 24 +++++++++++++++++++++---
migration/options.c | 25 +++++++++++++++++++++++++
migration/trace-events | 2 +-
7 files changed, 75 insertions(+), 5 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-05 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 19:38 Peter Xu [this message]
2023-09-05 19:38 ` [PATCH v3 1/1] migration: Allow user to specify available switchover bandwidth Peter Xu
2023-09-09 14:41 ` Joao Martins
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=20230905193802.250440-1-peterx@redhat.com \
--to=peterx@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=lei4.wang@intel.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 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).