From: Peter Xu <peterx@redhat.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Cc: farosas@suse.de, yuan1.liu@intel.com, qemu-devel@nongnu.org,
linuxarm@huawei.com, linwenkai6@hisilicon.com,
zhangfei.gao@linaro.org, huangchenghai2@huawei.com
Subject: Re: [PATCH 0/7] Live migration acceleration with UADK
Date: Tue, 4 Jun 2024 16:59:56 -0400 [thread overview]
Message-ID: <Zl-ATAeH-hZ6IFHz@x1n> (raw)
In-Reply-To: <20240529094435.11140-1-shameerali.kolothum.thodi@huawei.com>
On Wed, May 29, 2024 at 10:44:20AM +0100, Shameer Kolothum via wrote:
> Hi,
>
> This series adds support for UADK library based hardware acceleration
> for live migration. UADK[0] is a general-purpose user space accelerator
> framework that uses shared virtual addressing (SVA) to provide a unified
> programming interface for hardware acceleration of cryptographic and
> compression algorithms.
>
> UADK makes use of the UACCE(Unified/User-space-access-intended Accelerator
> Framework) Linux kernel module which enables hardware accelerators from
> different vendors that support SVA to adapt to UADK. Linux kernel from
> v5.9 has support for UACCE and SVA on ARM64 platforms.
>
> Currently, HiSilicon Kunpeng hardware accelerators have been registered with
> UACCE and the Zip accelerator on these platforms can be used for compression
> which can free up CPU computing power and improve computing performance.
>
> This series is on top of Intel IAA accelerator live migration support
> series[1] from Yuan Liu. Many thanks for doing this.
Just looked at the IAA series too, I didn't read multifd-*.[ch] much on
both sides but both the series look pretty clean to me.
Thanks,
--
Peter Xu
prev parent reply other threads:[~2024-06-04 21:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 9:44 [PATCH 0/7] Live migration acceleration with UADK Shameer Kolothum via
2024-05-29 9:44 ` [PATCH 1/7] docs/migration: add uadk compression feature Shameer Kolothum via
2024-05-30 13:25 ` Liu, Yuan1
2024-05-30 14:01 ` Shameerali Kolothum Thodi via
2024-05-30 14:13 ` Liu, Yuan1
2024-06-05 18:59 ` Fabiano Rosas
2024-05-29 9:44 ` [PATCH 2/7] configure: Add uadk option Shameer Kolothum via
2024-06-04 21:25 ` Fabiano Rosas
2024-05-29 9:44 ` [PATCH 3/7] migration/multifd: add uadk compression framework Shameer Kolothum via
2024-05-29 11:10 ` Markus Armbruster
2024-05-30 6:56 ` Shameerali Kolothum Thodi via
2024-06-04 21:24 ` Fabiano Rosas
2024-05-29 9:44 ` [PATCH 4/7] migration/multifd: Add UADK initialization Shameer Kolothum via
2024-06-05 14:58 ` Fabiano Rosas
2024-06-05 15:17 ` Shameerali Kolothum Thodi via
2024-05-29 9:44 ` [PATCH 5/7] migration/multifd: Add UADK based compression and decompression Shameer Kolothum via
2024-06-05 18:57 ` Fabiano Rosas
2024-06-06 7:11 ` Shameerali Kolothum Thodi via
2024-05-29 9:44 ` [PATCH 6/7] migration/multifd: Switch to no compression when no hardware support Shameer Kolothum via
2024-06-05 19:08 ` Fabiano Rosas
2024-05-29 9:44 ` [PATCH 7/7] tests/migration-test: add uadk compression test Shameer Kolothum via
2024-06-05 19:18 ` Fabiano Rosas
2024-06-04 20:59 ` Peter Xu [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=Zl-ATAeH-hZ6IFHz@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=huangchenghai2@huawei.com \
--cc=linuxarm@huawei.com \
--cc=linwenkai6@hisilicon.com \
--cc=qemu-devel@nongnu.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yuan1.liu@intel.com \
--cc=zhangfei.gao@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.