From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Akhil Goyal <gakhil@marvell.com>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
"acc@openeuler.org" <acc@openeuler.org>
Subject: Re: [EXT] Re: crypto/uadk: introduce uadk crypto driver
Date: Thu, 20 Oct 2022 10:48:26 +0800 [thread overview]
Message-ID: <CABQgh9Fw+LQN99Y+Kgfq3F8H1joHQHR8rrR=OjKb7OvprUT7ng@mail.gmail.com> (raw)
In-Reply-To: <CABQgh9EhCPAe8ttAtkpmrj10uj1Dbs+EG1zBLuwaDQ_weYKdJQ@mail.gmail.com>
Hi, Akhil
On Wed, 19 Oct 2022 at 23:27, Zhangfei Gao <zhangfei.gao@linaro.org> 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.
> > >
> > > The udak library [1] now support x86 local build, and export pkg-config.
> > > I have verified the crypto pmd on both x86 and arm with pkg-config feature.
> > > Though x86 only support build and install, but not test since no hardware.
> > >
> > > v4: https://patches.dpdk.org/project/dpdk/cover/20221019125753.1700071-1-zhangfei.gao@linaro.org/
> > >
> > > [1] https://github.com/Linaro/uadk
> > >
> >
> > I am getting below error with openssl 3.0
> > Do you have a dependency with earlier versions in uadk? If so, can you fix configure.ac in uadk
> > to check for version and skip crypto if dependency is not met.
Thanks for the suggestion
>
> Oops, never thought about this.
>
> How about this
> https://github.com/Linaro/uadk/pull/516
The pull has been merged.
I have verified verified openssl3.0 (ignored) , openssl1.0.0 (ignored)
and openssl1.1.1f (works)
We are using openssl1.1.1f verison now.
Sorry for the inconvenience.
Thanks
prev parent reply other threads:[~2022-10-20 2:48 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
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 [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='CABQgh9Fw+LQN99Y+Kgfq3F8H1joHQHR8rrR=OjKb7OvprUT7ng@mail.gmail.com' \
--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).