From: "you.chen" <you.chen@intel.com>
To: qemu-devel@nongnu.org
Cc: "you.chen" <you.chen@intel.com>, "dennis . wu" <dennis.wu@intel.com>
Subject: [PATCH v2 0/2] migration: use qatzip to acclerate the live migration
Date: Mon, 17 Apr 2023 16:39:33 +0800 [thread overview]
Message-ID: <20230417083935.415782-1-you.chen@intel.com> (raw)
Changes in V2:
1. Added CONFIG_QATZIP macro to control this feature
2. removed useless code changes
3. fixed typos
WIP: tests still under development
Hello,
qatzip https://github.com/intel/QATzip is a project that
supply the zlib like api with the Intel QAT hardware.
compress and decompress performance with small data block
(4kb page) is low with qatzip API. so we compose multiple
pages into a multi page address structure which is a buffer
list, then we compose these pages together and then call
compress and decompress. we also expand the io_buf_size
since qat is fast have have stress to the IO_BUFF.
If there is no QAT hardware, qatzip will fall back to the
software with proper configuration. that mean if host server
have the QAT hardware, while destination server don't have QAT,
the live migration still work well.
To use the qatzip, one parameter is added in both host and
destination side:
(qemu) migrate_set_parameter compress-with-qat on
if you proper eabled the qatzip, then you can benefit from
the QAT acceleration.
Since the compress/decompress offloading to the QAT hardware,
no CPU resource needed (only a periodic polling need some CPU
resource).
For the performance, with the same threads scale, with QATzip
(HW), the live migration will have 2~4 time of performance.
Plan: so far qatzip API support SVM,but no batch APIs and the
requirement is raised. once the batch APIs ready, the perf expect
to reach close to 10x.
Co-developed-by: dennis.wu <dennis.wu@intel.com>
you.chen (2):
migration: add build option to support qemu build with qatzip
migration: add support for qatzip compression when doing live
migration
meson.build | 11 +-
meson_options.txt | 2 +
migration/migration-hmp-cmds.c | 4 +
migration/migration.c | 22 ++
migration/migration.h | 1 +
migration/qemu-file.c | 15 +-
migration/qemu-file.h | 5 +
migration/ram.c | 675 +++++++++++++++++++++++++++++----
qapi/migration.json | 8 +-
scripts/meson-buildoptions.sh | 3 +
10 files changed, 673 insertions(+), 73 deletions(-)
--
2.27.0
next reply other threads:[~2023-04-17 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 8:39 you.chen [this message]
2023-04-17 8:39 ` [PATCH v2 1/2] migration: add build option to support qemu build with qatzip you.chen
2023-04-17 9:04 ` Thomas Huth
2023-04-17 8:39 ` [PATCH v2 2/2] migration: add support for qatzip compression when doing live migration you.chen
2023-04-17 13:27 ` Markus Armbruster
2023-04-20 11:29 ` Juan Quintela
2023-04-18 7:49 ` 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=20230417083935.415782-1-you.chen@intel.com \
--to=you.chen@intel.com \
--cc=dennis.wu@intel.com \
--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).