[PATCH v2 0/2] migration: use qatzip to acclerate the live migration

you.chen posted 2 patches 1 year ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20230417083935.415782-1-you.chen@intel.com
Maintainers: Paolo Bonzini <pbonzini@redhat.com>, "Marc-André Lureau" <marcandre.lureau@redhat.com>, "Daniel P. Berrangé" <berrange@redhat.com>, Thomas Huth <thuth@redhat.com>, "Philippe Mathieu-Daudé" <philmd@linaro.org>, Juan Quintela <quintela@redhat.com>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>, Eric Blake <eblake@redhat.com>, Markus Armbruster <armbru@redhat.com>
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(-)
[PATCH v2 0/2] migration: use qatzip to acclerate the live migration
Posted by you.chen 1 year ago
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