From: Bruce Richardson <bruce.richardson@intel.com>
To: "mirzaei.reza" <mirzaei.reza@ut.ac.ir>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] building l2fwd-crypto example from Makefile
Date: Mon, 8 Feb 2021 16:37:02 +0000 [thread overview]
Message-ID: <20210208163702.GD2020@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <85f763d093a3d6e5a7a73f8eee9aa0c1@ut.ac.ir>
On Sun, Feb 07, 2021 at 12:46:50PM +0330, mirzaei.reza wrote:
> Hello,
>
> I have a problem to build l2fwd-crypto example using its Makefile. I
> build it using Makefile according to this [1] tutorial, when i run the
> compiled file using the following command:
>
> ./l2fwd-crypto -l 1 -n 4
> --vdev="crypto_aesni_mb,socket_id=0,max_nb_sessions=128" \
> -- -p 1 --cdev SW --chain CIPHER_HASH --cipher_algo "aes-cbc"
> --auth_algo "sha1-hmac"
>
> I get the follwing error:
>
> EAL: Detected 16 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: FAILED TO PARSE DEVICE "CRYPTO_AESNI_GCM"
> EAL: UNABLE TO PARSE DEVICE
> 'CRYPTO_AESNI_GCM,SOCKET_ID=0,MAX_NB_SESSIONS=128'
> EAL: ERROR - EXITING WITH CODE: 1
> CAUSE: INVALID EAL ARGUMENTS
>
> Could anyone help me to solve this problem?
>
> It's worth to noting that when i build it using meson and ninja as the
> following, it works successfuly.
>
> meson -Dexamples=l2fwd-crypto build
>
> Thanks in advance
>
As well as the response David provided which is pretty comprehensive, I
have just today hit some similar issues when trying to run a shared-linked
DPDK app, even when DPDK was installed system-wide. If you install DPDK in
e.g. /usr/local on your system and still see issues, can you perhaps test out
patch http://patches.dpdk.org/patch/87823/ and see if it helps.
Regards,
/Bruce
prev parent reply other threads:[~2021-02-08 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 9:16 mirzaei.reza
2021-02-07 10:26 ` David Marchand
2021-02-08 16:37 ` Bruce Richardson [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=20210208163702.GD2020@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mirzaei.reza@ut.ac.ir \
/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).