From: Akhil Goyal <gakhil@marvell.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>,
Declan Doherty <declan.doherty@intel.com>,
Fan Zhang <royzhang1980@gmail.com>,
Ashish Gupta <ashishg@marvell.com>, Ray Kinsella <mdr@ashroe.eu>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "acc@openeuler.org" <acc@openeuler.org>
Subject: RE: [EXT] [PATCH resend v5 0/6] crypto/uadk: introduce uadk crypto driver
Date: Tue, 25 Oct 2022 14:59:45 +0000 [thread overview]
Message-ID: <CO6PR18MB448406B64DAA20BFA3FEDA31D8319@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221024134409.1896776-1-zhangfei.gao@linaro.org>
> Introduce a new crypto PMD for hardware accelerators based on UADK [1].
>
> 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.
>
> [1] https://github.com/Linaro/uadk
>
> Test:
> sudo dpdk-test --vdev=crypto_uadk (--log-level=6)
> RTE>>cryptodev_uadk_autotest
> RTE>>quit
>
> resend:
> fix uadk lib, still use <uadk/wd_cipher.h>
There is nothing called as resend in DPDK ML.
Please simply increment version number each time you send the set.
Also add release notes update in the patch
where the driver implementation is complete.
Compilation issues are all done now.
Have sent some other comments on the patches. Please send the v6 ASAP.
We need to close RC2 in a couple of days.
>
> Update in v5
> Patch 1 fix the build issue when uadk is installed to specific folder
> And update doc accordingly
>
> Update in v4:
> Akril suggest dpdk use pkg-config, So
> Enable uadk support x86 local build, and support pkg-config.
> Use pkg-config feature for the uadk crypto pmd.
> Add build uadk library steps in doc
> Test on both x86 and arm.
> x86 can build and install, but can not test since no device.
>
> Resend v3:
> Rebase on next/for-main, which just merged the series
> "cryptodev: rework session framework".
>
> Update in v3:
> Split patches according to Akhil's suggestions
> Please split the patches as below.
> 1. introduce driver - create files with meson.build and with probe/remove
> and device ops defined but not implemented.
> You do not need to write empty functions.
> Add basic documentation also which defines what the driver is.
> You can explain the build dependency here.
> 2. define queue structs and setup/remove APIs
> 3. Add data path
> 4. implement cipher op. Add capabilities and documentation of what is
> supported in each of the patches. Add feature flags etc.
> 5. implement auth, add capabilities and documentation
> 6. test app changes.
>
> Update in v2:
> Change uadk_supported_platform to uadk_crypto_version, which matches
> better
> than platform.
> enum uadk_crypto_version {
> UADK_CRYPTO_V2,
> UADK_CRYPTO_V3,
> };
>
> Update in v1, compared 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 (6):
> crypto/uadk: introduce uadk crypto driver
> crypto/uadk: support basic operations
> crypto/uadk: support enqueue/dequeue operations
> crypto/uadk: support cipher algorithms
> crypto/uadk: support auth algorithms
> test/crypto: add cryptodev_uadk_autotest
>
> MAINTAINERS | 6 +
> app/test/test_cryptodev.c | 7 +
> app/test/test_cryptodev.h | 1 +
> doc/guides/cryptodevs/features/uadk.ini | 55 ++
> doc/guides/cryptodevs/index.rst | 1 +
> doc/guides/cryptodevs/uadk.rst | 94 ++
> drivers/crypto/meson.build | 1 +
> drivers/crypto/uadk/meson.build | 30 +
> drivers/crypto/uadk/uadk_crypto_pmd.c | 1141 +++++++++++++++++++++++
> drivers/crypto/uadk/version.map | 3 +
> 10 files changed, 1339 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
>
> --
> 2.38.1
next prev parent reply other threads:[~2022-10-25 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 13:44 Zhangfei Gao
2022-10-24 13:44 ` [PATCH resend v5 1/6] " Zhangfei Gao
2022-10-25 14:08 ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 2/6] crypto/uadk: support basic operations Zhangfei Gao
2022-10-25 14:18 ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 3/6] crypto/uadk: support enqueue/dequeue operations Zhangfei Gao
2022-10-24 13:44 ` [PATCH resend v5 4/6] crypto/uadk: support cipher algorithms Zhangfei Gao
2022-10-25 14:28 ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 5/6] crypto/uadk: support auth algorithms Zhangfei Gao
2022-10-25 14:38 ` [EXT] " Akhil Goyal
2022-10-26 10:02 ` Zhangfei Gao
2022-10-24 13:44 ` [PATCH resend v5 6/6] test/crypto: add cryptodev_uadk_autotest Zhangfei Gao
2022-10-25 14:54 ` [EXT] " Akhil Goyal
2022-10-26 9:57 ` Zhangfei Gao
2022-10-25 14:59 ` Akhil Goyal [this message]
2022-10-26 9:53 ` [EXT] [PATCH resend v5 0/6] crypto/uadk: introduce uadk crypto driver Zhangfei Gao
2022-10-26 10:16 ` Akhil Goyal
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=CO6PR18MB448406B64DAA20BFA3FEDA31D8319@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=acc@openeuler.org \
--cc=ashishg@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
--cc=royzhang1980@gmail.com \
--cc=thomas@monjalon.net \
--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).