From: Thenveer Poolakkanni <thenveer.poolakkanni@iwave-global.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Ayshathul Thuhara <ayshathul.thuhara@iwave-global.com>,
Nafiah Siddiqha <nafiah.siddiqha@iwave-global.com>
Subject: L2 cryptography example application using nfb driver .
Date: Tue, 11 Feb 2025 06:44:33 +0000 [thread overview]
Message-ID: <PN3P287MB027397F7057BDC5384DFE3F5B7FD2@PN3P287MB0273.INDP287.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
Hi ,
I am using dpdk-23.11-rc1 version and nfb driver .
When i am running l2fwd-crypto example application , getting the below error ,
[image]
missing function definitions for - rte_cryptodev_get_cipher_algo_string , rte_cryptodev_get_auth_algo_string, and rte_cryptodev_get_aead_algo_string .
so , i added these function definitions as below ,
[image]
Now , its compiling and running , but showing no ethernet ports available .
[image]
I am running with below command line
sudo ./build/l2fwd-crypto -l 0-1 --vdev "crypto_openssl0" --vdev "crypto_openssl1" -d librte_crypto_openssl.so -- -p 0x3 --chain CIPHER_HASH --cipher_op ENCRYPT --cipher_algo aes-cbc --cipher_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f --auth_op GENERATE --auth_algo sha1-hmac --auth_key
10:11:12:13:14:15:16:17:18:19:1a:1b:1c:1d:1e:1f
Can you help me out with this by providing any patch files for l2fwd-crypto application .
Thanks in advance
best regards
Thenveer Poolakkanni.
[-- Attachment #1.2: Type: text/html, Size: 3419 bytes --]
[-- Attachment #2: image.png --]
[-- Type: image/jpeg, Size: 47466 bytes --]
[-- Attachment #3: image.png --]
[-- Type: image/jpeg, Size: 27316 bytes --]
[-- Attachment #4: image.png --]
[-- Type: image/jpeg, Size: 20136 bytes --]
reply other threads:[~2025-02-11 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=PN3P287MB027397F7057BDC5384DFE3F5B7FD2@PN3P287MB0273.INDP287.PROD.OUTLOOK.COM \
--to=thenveer.poolakkanni@iwave-global.com \
--cc=ayshathul.thuhara@iwave-global.com \
--cc=dev@dpdk.org \
--cc=nafiah.siddiqha@iwave-global.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).