From: Prasad Pandit <ppandit@redhat.com>
To: qemu-devel@nongnu.org
Cc: peterx@redhat.com, farosas@suse.de, berrange@redhat.com,
Prasad Pandit <pjp@fedoraproject.org>
Subject: [PATCH v2 0/3] Allow to enable multifd and postcopy migration together
Date: Fri, 29 Nov 2024 17:52:53 +0530 [thread overview]
Message-ID: <20241129122256.96778-1-ppandit@redhat.com> (raw)
From: Prasad Pandit <pjp@fedoraproject.org>
Hello,
* Currently Multifd and Postcopy migration can not be used together.
QEMU shows "Postcopy is not yet compatible with multifd" message.
When migrating guests with large (100's GB) RAM, Multifd threads
help to accelerate migration, but inability to use it with the
Postcopy mode delays guest start up on the destination side.
* This patch series allows to enable both Multifd and Postcopy
migration together. Precopy and Multifd threads work during
the initial guest (RAM) transfer. When migration moves to the
Postcopy phase, Multifd threads are restrained and the Postcopy
threads start to request pages from the source side.
* This series removes magic value (4-bytes) introduced in the
previous series for the Postcopy channel. And refactoring of
the 'ram_save_target_page' function is made independent of
the multifd & postcopy change.
v1: https://lore.kernel.org/qemu-devel/20241126115748.118683-1-ppandit@redhat.com/T/#u
v0: https://lore.kernel.org/qemu-devel/20241029150908.1136894-1-ppandit@redhat.com/T/#u
Thank you.
---
Prasad Pandit (3):
migration/multifd: move macros to multifd header
migration: refactor ram_save_target_page functions
migration: enable multifd and postcopy together
migration/migration.c | 90 +++++++++++++++++++++++---------------
migration/multifd-nocomp.c | 3 +-
migration/multifd.c | 5 ---
migration/multifd.h | 5 +++
migration/options.c | 5 ---
migration/ram.c | 73 +++++++++----------------------
6 files changed, 82 insertions(+), 99 deletions(-)
--
2.47.1
next reply other threads:[~2024-11-29 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 12:22 Prasad Pandit [this message]
2024-11-29 12:22 ` [PATCH v2 1/3] migration/multifd: move macros to multifd header Prasad Pandit
2024-12-09 21:07 ` Fabiano Rosas
2024-11-29 12:22 ` [PATCH v2 2/3] migration: refactor ram_save_target_page functions Prasad Pandit
2024-11-29 12:22 ` [PATCH v2 3/3] migration: enable multifd and postcopy together Prasad Pandit
2024-11-29 16:45 ` [PATCH v2 0/3] Allow to enable multifd and postcopy migration together Peter Xu
2024-12-02 7:07 ` Prasad Pandit
2024-12-05 22:41 ` Peter Xu
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=20241129122256.96778-1-ppandit@redhat.com \
--to=ppandit@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=qemu-devel@nongnu.org \
/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).