From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Akhil Goyal <gakhil@marvell.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
"acc@openeuler.org" <acc@openeuler.org>
Subject: Re: crypto/uadk: introduce uadk crypto driver
Date: Mon, 17 Oct 2022 22:02:06 +0800 [thread overview]
Message-ID: <9e897e5c-b6db-bea7-3490-b57c1f76a8ba@linaro.org> (raw)
In-Reply-To: <CO6PR18MB44848DBA263658B2245AA71ED8299@CO6PR18MB4484.namprd18.prod.outlook.com>
Hi, Akhil
On 2022/10/17 下午3:02, Akhil Goyal wrote:
>
> Hi everyone,
>
> We have a new crypto PMD submitted on ML
> (http://patches.dpdk.org/project/dpdk/cover/20221008083747.6559-1-zhangfei.gao@linaro.org/)
>
> This PMD is dependent on an external library which needs to be cross
> compiled for ARM on x86.
>
> It mandatorily need “numactl” also cross-compiled and instead of using
> pkg-config of libnuma, it need the library and headers to be copied
> manually to aarch toolchain.
>
> And if that is also done, it is not generating pkg-config which DPDK
> can use to compile the PMD.
>
Thanks for the guidance
We are trying to provide pkgconfig file for uadk libs
https://github.com/Linaro/uadk/pull/513
And have fixed the x86 local build.
https://github.com/Linaro/uadk/pull/512
Though currently uadk crypto pmd is targeting for ARM,
So add build dependency (dpdk_conf.get('RTE_ARCH_64')) in meson.build
Thanks
> So the question is whether we can accept the PMD without pkg-config
> and along with above dependency?
>
> Regards,
>
> Akhil
>
next prev parent reply other threads:[~2022-10-17 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 7:02 Akhil Goyal
2022-10-17 14:02 ` Zhangfei Gao [this message]
2022-10-18 10:07 ` Zhangfei Gao
2022-10-18 10:52 ` Zhangfei Gao
2022-10-19 6:55 ` Thomas Monjalon
2022-10-19 7:24 ` Zhangfei Gao
2022-10-19 13:19 ` Zhangfei Gao
2022-10-19 14:25 ` [EXT] " Akhil Goyal
2022-10-19 15:27 ` Zhangfei Gao
2022-10-20 2:48 ` 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=9e897e5c-b6db-bea7-3490-b57c1f76a8ba@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=acc@openeuler.org \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=techboard@dpdk.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).