From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Kudupudi, Ugendreshwar" <Ugendreshwar.Kudupudi@cavium.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] OpenSSL Crypto PMD Fails
Date: Fri, 27 Apr 2018 10:19:29 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B4358938E8F4@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <BN3PR0701MB114012ABFBB69D52E1743B5A8C8F0@BN3PR0701MB1140.namprd07.prod.outlook.com>
It's not enabled by default - have you enabled it in the config file?
sed -i 's,\(CONFIG_RTE_LIBRTE_PMD_OPENSSL\)=n,\1=y,' $RTE_OUTPUT/.config
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Kudupudi, Ugendreshwar
> Sent: Wednesday, April 25, 2018 2:24 PM
> To: users@dpdk.org
> Subject: [dpdk-users] OpenSSL Crypto PMD Fails
>
> Hello Team
>
> We are looking to execute the sample OpenSSL Crypto PMD and got the below error.
>
> Environment Details:
> -----------------------------
>
> OS: Centos 7.3 (3.10.0)
> DPDK: 17.11.2
> OpenSSL Version: 1.0.2k-fips
> Ethernet: Intel X710
> Isolcpu: 0-3
> Link: https://dpdk.org/doc/guides/cryptodevs/openssl.html
>
> Any help in resolving this issue is deeply appreciated.
>
> ----------------------------------------- log start ----------------------------------------------------------------------------------
> sudo ./examples/l2fwd-crypto/build/l2fwd-crypto -l 0-1 -n 4 --vdev crypto_openssl -- -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 --iv 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:ff --
> auth_op GENERATE --auth_algo SHA1_HMAC --auth_key
> 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:
> 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11
> EAL: Detected 28 lcore(s)
> ERROR: failed to parse device "crypto_openssl"
> EAL: Unable to parse device 'crypto_openssl'
> EAL: Error - exiting with code: 1
> Cause: Invalid EAL arguments
> ----------------------------------------- log end ----------------------------------------------------------------------------------
>
>
>
> We ran the NULL Crypto PMD successfully though.
>
>
>
> ----------------------------------------- log start ----------------------------------------------------------------------------------
>
> sudo ./examples/l2fwd-crypto/build/l2fwd-crypto -l 1 -n 4 --
> vdev=crypto_null,socket_id=0,max_nb_sessions=128 -- -p 1 --cdev SW --chain CIPHER_ONLY --cipher_algo
> null
> EAL: Detected 28 lcore(s)
> EAL: Probing VFIO support...
> EAL: VFIO support initialized
> EAL: PCI device 0000:01:00.0 on NUMA socket 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:01:00.1 on NUMA socket 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:02:00.0 on NUMA socket 0
> EAL: probe driver: 8086:1572 net_i40e
> EAL: using IOMMU type 1 (Type 1)
> PMD: Global register is changed during enable FDIR flexible payload
> PMD: Global register is changed during support QinQ parser
> PMD: Global register is changed during configure hash input set
> PMD: Global register is changed during configure fdir mask
> PMD: Global register is changed during configure hash mask
> PMD: Global register is changed during support QinQ cloud filter
> PMD: Global register is changed during support TPID configuration
> EAL: PCI device 0000:02:00.1 on NUMA socket 0
> EAL: probe driver: 8086:1572 net_i40e
> CRYPTODEV: [crypto_null] - Creating cryptodev crypto_null
>
> CRYPTODEV: [crypto_null] - Initialisation parameters - name: crypto_null,socket id: 0, max queue pairs: 8,
> max sessions: 128
> MAC updating enabled
> Initializing port 0... Port 0, MAC address: 3C:FD:FE:0D:1C:E0
>
>
> Checking link status..........................................................................................done
> Port 0 Link Down
> Lcore 1: RX port 0
> Allocated session pool on socket 0
> Lcore 1: cryptodev 0
> L2FWD: entering main loop on lcore 1
> L2FWD: -- lcoreid=1 portid=0
> L2FWD: -- lcoreid=1 cryptoid=0
> Options:-
> nportmask: 1
> ports per lcore: 1
> refresh period : 10000
> single lcore mode: disabled
> stats_printing: enabled
> sessionless crypto: disabled
>
> Crypto chain: Input --> Encrypt --> Output
>
> ---- Cipher information ---
> Algorithm: null
> Cipher key: at [0x7fedbff38080], len=0
> IV: at [0x7fedbff34640], len=0
>
> Port statistics ====================================
> Statistics for port 0 ------------------------------
> Packets sent: 0
> Packets received: 0
> Packets dropped: 0
> Crypto statistics ==================================
> Statistics for cryptodev 0 -------------------------
> Packets enqueued: 0
> Packets dequeued: 0
> Packets errors: 0
> Aggregate statistics ===============================
> Total packets received: 0
> Total packets enqueued: 0
> Total packets dequeued: 0
> Total packets sent: 0
> Total packets dropped: 0
> Total packets crypto errors: 0
> ====================================================
> ----------------------------------------- log end ----------------------------------------------------------------------------------
>
>
> Regards
> Ugen
next prev parent reply other threads:[~2018-04-27 10:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 13:23 Kudupudi, Ugendreshwar
2018-04-27 10:19 ` Trahe, Fiona [this message]
2018-04-27 10:23 ` Kudupudi, Ugendreshwar
2018-04-27 10:30 ` Trahe, Fiona
2018-04-30 11:22 ` Kudupudi, Ugendreshwar
2018-05-04 10:09 ` Kudupudi, Ugendreshwar
2018-05-08 9:58 ` Trahe, Fiona
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=348A99DA5F5B7549AA880327E580B4358938E8F4@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=Ugendreshwar.Kudupudi@cavium.com \
--cc=users@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).