From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Akhil Goyal <gakhil@marvell.com>,
Declan Doherty <declan.doherty@intel.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
Ashish Gupta <ashishg@marvell.com>, Ray Kinsella <mdr@ashroe.eu>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "acc@openeuler.org" <acc@openeuler.org>
Subject: Re: [EXT] [PATCH v2 2/5] crypto/uadk: introduce uadk crypto driver
Date: Tue, 27 Sep 2022 17:57:49 +0800 [thread overview]
Message-ID: <ae6e1927-bc66-aef7-2e72-c433b0310589@linaro.org> (raw)
In-Reply-To: <CO6PR18MB44841BE40C5F3ABDDDC3CEBAD8529@CO6PR18MB4484.namprd18.prod.outlook.com>
On 2022/9/26 下午4:36, Akhil Goyal wrote:
>> 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.
>>
>> This patch adds the basic framework.
>>
>> [1] https://github.com/Linaro/uadk
>>
>> Test:
>> sudo dpdk-test --vdev=crypto_uadk (--log-level=6)
>> RTE>>cryptodev_uadk_autotest
>> RTE>>quit
> Remove this test info. It can be in your last patch where test app changes are introduced.
>
>
>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>> ---
>> drivers/crypto/meson.build | 1 +
>> drivers/crypto/uadk/meson.build | 36 +++
>> drivers/crypto/uadk/uadk_crypto_pmd.c | 450 ++++++++++++++++++++++++++
>> drivers/crypto/uadk/version.map | 3 +
>> 4 files changed, 490 insertions(+)
>> 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
>>
>> diff --git a/drivers/crypto/meson.build b/drivers/crypto/meson.build
>> index 147b8cf633..ee5377deff 100644
>> --- a/drivers/crypto/meson.build
>> +++ b/drivers/crypto/meson.build
>> @@ -18,6 +18,7 @@ drivers = [
>> 'octeontx',
>> 'openssl',
>> 'scheduler',
>> + 'uadk',
>> 'virtio',
>> ]
>>
>> diff --git a/drivers/crypto/uadk/meson.build b/drivers/crypto/uadk/meson.build
>> new file mode 100644
>> index 0000000000..a67c6c7ca5
>> --- /dev/null
>> +++ b/drivers/crypto/uadk/meson.build
>> @@ -0,0 +1,36 @@
>> +# SPDX-License-Identifier: BSD-3-Clause
>> +# Copyright 2022-2023 Huawei Technologies Co.,Ltd. All rights reserved.
>> +# Copyright 2022-2023 Linaro ltd.
>> +
>> +if not is_linux
>> + build = false
>> + reason = 'only supported on Linux'
>> + subdir_done()
>> +endif
>> +
>> +if arch_subdir != 'arm' or not dpdk_conf.get('RTE_ARCH_64')
>> + build = false
>> + reason = 'only supported on aarch64'
>> + subdir_done()
>> +endif
>> +
>> +sources = files(
>> + 'uadk_crypto_pmd.c',
>> +)
>> +
>> +deps += 'bus_vdev'
>> +dep = cc.find_library('libwd_crypto', dirs: ['/usr/local/lib'], required: false)
> I believe dirs is not required. You cannot assume that the lib is installed in /usr/local/lib/.
> Check other PMDs which have such dependencies. Eg. Ipsec-mb
Double checked,
This is workable via setting env for building.
export LIBRARY_PATH=/usr/local/lib
Thanks
next prev parent reply other threads:[~2022-09-27 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 2:40 [PATCH v2 0/5] " Zhangfei Gao
2022-09-23 2:40 ` [PATCH v2 1/5] test/crypto: add cryptodev_uadk_autotest Zhangfei Gao
2022-09-26 7:59 ` [EXT] " Akhil Goyal
2022-09-23 2:40 ` [PATCH v2 2/5] crypto/uadk: introduce uadk crypto driver Zhangfei Gao
2022-09-26 8:36 ` [EXT] " Akhil Goyal
2022-09-26 9:10 ` Zhangfei Gao
2022-09-27 9:57 ` Zhangfei Gao [this message]
2022-09-29 3:36 ` Zhangfei Gao
2022-09-23 2:40 ` [PATCH v2 3/5] crypto/uadk: support cipher algorithms Zhangfei Gao
2022-09-23 2:40 ` [PATCH v2 4/5] crypto/uadk: support auth algorithms Zhangfei Gao
2022-09-23 2:40 ` [PATCH v2 5/5] doc: Update doc for UADK crypto PMD 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=ae6e1927-bc66-aef7-2e72-c433b0310589@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=acc@openeuler.org \
--cc=ashishg@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 \
/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).