From: liulongfang <liulongfang@huawei.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>,
Akhil Goyal <gakhil@marvell.com>,
Declan Doherty <declan.doherty@intel.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
Ashish Gupta <ashish.gupta@marvell.com>,
"Ray Kinsella" <mdr@ashroe.eu>
Cc: <dev@dpdk.org>, <acc@openeuler.org>
Subject: Re: [Acc] [PATCH 0/5] crypto/uadk: introduce uadk crypto driver
Date: Tue, 13 Sep 2022 15:08:57 +0800 [thread overview]
Message-ID: <ee18a65a-4ee3-b74e-d654-8199bfdddeed@huawei.com> (raw)
In-Reply-To: <20220911052344.31239-1-zhangfei.gao@linaro.org>
On 2022/9/11 13:23, Zhangfei Gao wrote:
> Introduce a new crypto PMD for UADK, which relies on UADK library [1].
>
This should be "a new crypto PMD for DPDK"
> UADK is a framework for user applications to access hardware accelerators.
> UADK relies on IOMMU SVA (Shared Virtual Address) feature, which share
> the same page table between IOMMU and MMU.
> Thereby user application can directly use virtual address for device dma,
> which enhances the performance as well as easy usability.
>
> Currently supported platforms:
> HiSilicon kunpeng920 & kunpeng930.
>
> This patch adds a basic framework.
>
> [1] https://github.com/Linaro/uadk
>
> Test:
> sudo dpdk-test --vdev=crypto_uadk (--log-level=6)
> RTE>>cryptodev_uadk_autotest
> RTE>>quit
>
> Update with rfc
>
> Suggested from Akhil Goyal <gakhil@marvell.com>
> Only consider crypto PMD first
> Split patch into small (individually compiled) patches.
> Update MAINTAINERS and doc/guides/cryptodevs/features/uadk.ini
>
> Zhangfei Gao (5):
> test/crypto: add cryptodev_uadk_autotest
> crypto/uadk: introduce uadk crypto driver
> crypto/uadk: support cipher algorithms
> crypto/uadk: support auth algorithms
> doc: Update doc for UADK crypto PMD
>
> MAINTAINERS | 6 +
> app/test/test_cryptodev.c | 7 +
> app/test/test_cryptodev.h | 1 +
> doc/guides/cryptodevs/features/uadk.ini | 54 ++
> doc/guides/cryptodevs/index.rst | 1 +
> doc/guides/cryptodevs/uadk.rst | 80 ++
> drivers/crypto/meson.build | 1 +
> drivers/crypto/uadk/meson.build | 36 +
> drivers/crypto/uadk/uadk_crypto_pmd.c | 1161 +++++++++++++++++++++++
> drivers/crypto/uadk/version.map | 3 +
> 10 files changed, 1350 insertions(+)
> create mode 100644 doc/guides/cryptodevs/features/uadk.ini
> create mode 100644 doc/guides/cryptodevs/uadk.rst
> create mode 100644 drivers/crypto/uadk/meson.build
> create mode 100644 drivers/crypto/uadk/uadk_crypto_pmd.c
> create mode 100644 drivers/crypto/uadk/version.map
>
Thanks,
Longfang
next prev parent reply other threads:[~2022-09-13 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 5:23 Zhangfei Gao
2022-09-11 5:23 ` [PATCH 1/5] test/crypto: add cryptodev_uadk_autotest Zhangfei Gao
2022-09-11 5:23 ` [PATCH 2/5] crypto/uadk: introduce uadk crypto driver Zhangfei Gao
2022-09-11 5:23 ` [PATCH 3/5] crypto/uadk: support cipher algorithms Zhangfei Gao
2022-09-11 5:23 ` [PATCH 4/5] crypto/uadk: support auth algorithms Zhangfei Gao
2022-09-11 5:23 ` [PATCH 5/5] doc: Update doc for UADK crypto PMD Zhangfei Gao
2022-09-13 7:08 ` liulongfang [this message]
2022-09-15 3:02 ` [Acc] [PATCH 0/5] crypto/uadk: introduce uadk crypto driver Zhangfei Gao
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=ee18a65a-4ee3-b74e-d654-8199bfdddeed@huawei.com \
--to=liulongfang@huawei.com \
--cc=acc@openeuler.org \
--cc=ashish.gupta@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=mdr@ashroe.eu \
--cc=roy.fan.zhang@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 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).