* [dpdk-users] OpenSSL Crypto PMD Fails @ 2018-04-25 13:23 Kudupudi, Ugendreshwar 2018-04-27 10:19 ` Trahe, Fiona 0 siblings, 1 reply; 7+ messages in thread From: Kudupudi, Ugendreshwar @ 2018-04-25 13:23 UTC (permalink / raw) To: users 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] OpenSSL Crypto PMD Fails 2018-04-25 13:23 [dpdk-users] OpenSSL Crypto PMD Fails Kudupudi, Ugendreshwar @ 2018-04-27 10:19 ` Trahe, Fiona 2018-04-27 10:23 ` Kudupudi, Ugendreshwar 0 siblings, 1 reply; 7+ messages in thread From: Trahe, Fiona @ 2018-04-27 10:19 UTC (permalink / raw) To: Kudupudi, Ugendreshwar, users 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] OpenSSL Crypto PMD Fails 2018-04-27 10:19 ` Trahe, Fiona @ 2018-04-27 10:23 ` Kudupudi, Ugendreshwar 2018-04-27 10:30 ` Trahe, Fiona 0 siblings, 1 reply; 7+ messages in thread From: Kudupudi, Ugendreshwar @ 2018-04-27 10:23 UTC (permalink / raw) To: Trahe, Fiona, users Yes. I did. # Compile PMD for Software backed device CONFIG_RTE_LIBRTE_PMD_OPENSSL=y CONFIG_RTE_LIBRTE_PMD_OPENSSL_DEBUG=n -ugen -----Original Message----- From: Trahe, Fiona [mailto:fiona.trahe@intel.com] Sent: 27 April 2018 15:49 To: Kudupudi, Ugendreshwar <Ugendreshwar.Kudupudi@cavium.com>; users@dpdk.org Subject: RE: OpenSSL Crypto PMD Fails 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:1 > 1: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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] OpenSSL Crypto PMD Fails 2018-04-27 10:23 ` Kudupudi, Ugendreshwar @ 2018-04-27 10:30 ` Trahe, Fiona 2018-04-30 11:22 ` Kudupudi, Ugendreshwar 0 siblings, 1 reply; 7+ messages in thread From: Trahe, Fiona @ 2018-04-27 10:30 UTC (permalink / raw) To: Kudupudi, Ugendreshwar, users Have you tried the unit tests? make test-build cd build/build/test/test /test -l1 -n1 > cryptodev_openssl_autotest > cryptodev_null_autotest > -----Original Message----- > From: Kudupudi, Ugendreshwar [mailto:Ugendreshwar.Kudupudi@cavium.com] > Sent: Friday, April 27, 2018 11:24 AM > To: Trahe, Fiona <fiona.trahe@intel.com>; users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > Yes. I did. > > # Compile PMD for Software backed device > CONFIG_RTE_LIBRTE_PMD_OPENSSL=y > CONFIG_RTE_LIBRTE_PMD_OPENSSL_DEBUG=n > > -ugen > > -----Original Message----- > From: Trahe, Fiona [mailto:fiona.trahe@intel.com] > Sent: 27 April 2018 15:49 > To: Kudupudi, Ugendreshwar <Ugendreshwar.Kudupudi@cavium.com>; users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > 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:1 > > 1: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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] OpenSSL Crypto PMD Fails 2018-04-27 10:30 ` Trahe, Fiona @ 2018-04-30 11:22 ` Kudupudi, Ugendreshwar 2018-05-04 10:09 ` Kudupudi, Ugendreshwar 0 siblings, 1 reply; 7+ messages in thread From: Kudupudi, Ugendreshwar @ 2018-04-30 11:22 UTC (permalink / raw) To: Trahe, Fiona, users Following is the log of autotest and l2fwd-crypto. RTE>>cryptodev_openssl_autotest + ------------------------------------------------------- + + Test Suite : Crypto Device OPENSSL Unit Test Suite + ------------------------------------------------------- + + TestCase [ 0] : test_multi_session succeeded + TestCase [ 1] : test_multi_session_random_usage succeeded 0) TestCase AES-128-CTR HMAC-SHA1 Encryption Digest PASS 1) TestCase AES-128-CTR HMAC-SHA1 Decryption Digest Verify PASS 2) TestCase AES-256-CTR HMAC-SHA1 Encryption Digest PASS 3) TestCase AES-256-CTR HMAC-SHA1 Decryption Digest Verify PASS 4) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest PASS 5) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest Scatter Gather PASS 6) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify PASS 7) TestCase AES-128-CBC HMAC-SHA256 Encryption Digest PASS 8) TestCase AES-128-CBC HMAC-SHA256 Decryption Digest Verify PASS 9) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest PASS 10) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest Sessionless PASS 11) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest Scatter Gather Sessionless PASS 12) TestCase AES-128-CBC HMAC-SHA512 Decryption Digest Verify PASS 13) TestCase AES-128-CBC HMAC-SHA512 Decryption Digest Verify Scatter Gather PASS 14) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest OOP PASS 15) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify OOP PASS 16) TestCase AES-128-CBC HMAC-SHA224 Encryption Digest PASS 17) TestCase AES-128-CBC HMAC-SHA224 Decryption Digest Verify PASS 18) TestCase AES-128-CBC HMAC-SHA384 Encryption Digest PASS 19) TestCase AES-128-CBC HMAC-SHA384 Decryption Digest Verify PASS 20) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest Sessionless PASS 21) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify Sessionless PASS + TestCase [ 2] : test_AES_chain_openssl_all succeeded 0) TestCase AES-128-CBC Encryption PASS 1) TestCase AES-128-CBC Decryption PASS 2) TestCase AES-192-CBC Encryption PASS 3) TestCase AES-192-CBC Encryption Scater gather PASS 4) TestCase AES-192-CBC Decryption PASS 5) TestCase AES-256-CBC Encryption PASS 6) TestCase AES-256-CBC Decryption PASS 7) TestCase AES-256-CBC OOP Encryption PASS 8) TestCase AES-256-CBC OOP Decryption PASS 9) TestCase AES-128-CTR Encryption PASS 10) TestCase AES-128-CTR Decryption PASS 11) TestCase AES-192-CTR Encryption PASS 12) TestCase AES-192-CTR Decryption PASS 13) TestCase AES-256-CTR Encryption PASS 14) TestCase AES-256-CTR Decryption PASS + TestCase [ 3] : test_AES_cipheronly_openssl_all succeeded 0) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest PASS 1) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify PASS 2) TestCase 3DES-128-CBC SHA1 Encryption Digest PASS 3) TestCase 3DES-128-CBC SHA1 Decryption Digest Verify PASS 4) TestCase 3DES-192-CBC HMAC-SHA1 Encryption Digest PASS 5) TestCase 3DES-192-CBC HMAC-SHA1 Decryption Digest Verify PASS 6) TestCase 3DES-192-CBC SHA1 Encryption Digest PASS 7) TestCase 3DES-192-CBC SHA1 Decryption Digest Verify PASS 8) TestCase 3DES-128-CTR HMAC-SHA1 Encryption Digest PASS 9) TestCase 3DES-128-CTR HMAC-SHA1 Decryption Digest Verify PASS 10) TestCase 3DES-128-CTR SHA1 Encryption Digest PASS 11) TestCase 3DES-128-CTR SHA1 Decryption Digest Verify PASS 12) TestCase 3DES-192-CTR HMAC-SHA1 Encryption Digest PASS 13) TestCase 3DES-192-CTR HMAC-SHA1 Decryption Digest Verify PASS 14) TestCase 3DES-192-CTR SHA1 Encryption Digest PASS 15) TestCase 3DES-192-CTR SHA1 Decryption Digest Verify PASS 16) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest OOP PASS 17) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify OOP PASS 18) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest Sessionless PASS 19) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify Sessionless PASS + TestCase [ 4] : test_3DES_chain_openssl_all succeeded 0) TestCase 3DES-128-CBC Encryption PASS 1) TestCase 3DES-128-CBC Decryption PASS 2) TestCase 3DES-192-CBC Encryption PASS 3) TestCase 3DES-192-CBC Decryption PASS 4) TestCase 3DES-128-CTR Encryption PASS 5) TestCase 3DES-128-CTR Decryption PASS 6) TestCase 3DES-192-CTR Encryption PASS 7) TestCase 3DES-192-CTR Decryption PASS + TestCase [ 5] : test_3DES_cipheronly_openssl_all succeeded 0) TestCase DES-CBC Encryption PASS 1) TestCase DES-CBC Decryption PASS + TestCase [ 6] : test_DES_cipheronly_openssl_all succeeded 0) TestCase DES-DOCSIS-BPI Full Block Encryption PASS 1) TestCase DES-DOCSIS-BPI Runt Block Encryption PASS 2) TestCase DES-DOCSIS-BPI Uneven Encryption PASS 3) TestCase DES-DOCSIS-BPI Full Block Decryption PASS 4) TestCase DES-DOCSIS-BPI Runt Block Decryption PASS 5) TestCase DES-DOCSIS-BPI Uneven Decryption PASS 6) TestCase DES-DOCSIS-BPI OOP Full Block Encryption PASS 7) TestCase DES-DOCSIS-BPI OOP Runt Block Encryption PASS 8) TestCase DES-DOCSIS-BPI OOP Uneven Encryption PASS 9) TestCase DES-DOCSIS-BPI OOP Full Block Decryption PASS 10) TestCase DES-DOCSIS-BPI OOP Runt Block Decryption PASS 11) TestCase DES-DOCSIS-BPI OOP Uneven Decryption PASS + TestCase [ 7] : test_DES_docsis_openssl_all succeeded 0) TestCase MD5 Digest PASS 1) TestCase MD5 Digest Verify PASS 2) TestCase HMAC-MD5 Digest PASS 3) TestCase HMAC-MD5 Digest Verify PASS 4) TestCase SHA1 Digest PASS 5) TestCase SHA1 Digest Verify PASS 6) TestCase HMAC-SHA1 Digest PASS 7) TestCase HMAC-SHA1 Digest Verify PASS 8) TestCase SHA224 Digest PASS 9) TestCase SHA224 Digest Verify PASS 10) TestCase HMAC-SHA224 Digest PASS 11) TestCase HMAC-SHA224 Digest Verify PASS 12) TestCase SHA256 Digest PASS 13) TestCase SHA256 Digest Verify PASS 14) TestCase HMAC-SHA256 Digest PASS 15) TestCase HMAC-SHA256 Digest Verify PASS 16) TestCase SHA384 Digest PASS 17) TestCase SHA384 Digest Verify PASS 18) TestCase HMAC-SHA384 Digest PASS 19) TestCase HMAC-SHA384 Digest Verify PASS 20) TestCase SHA512 Digest PASS 21) TestCase SHA512 Digest Verify PASS 22) TestCase HMAC-SHA512 Digest PASS 23) TestCase HMAC-SHA512 Digest Verify PASS + TestCase [ 8] : test_authonly_openssl_all succeeded + TestCase [ 9] : test_AES_GCM_authenticated_encryption_test_case_1 succeeded + TestCase [10] : test_AES_GCM_authenticated_encryption_test_case_2 succeeded + TestCase [11] : test_AES_GCM_authenticated_encryption_test_case_3 succeeded + TestCase [12] : test_AES_GCM_authenticated_encryption_test_case_4 succeeded + TestCase [13] : test_AES_GCM_authenticated_encryption_test_case_5 succeeded + TestCase [14] : test_AES_GCM_authenticated_encryption_test_case_6 succeeded + TestCase [15] : test_AES_GCM_authenticated_encryption_test_case_7 succeeded + TestCase [16] : test_AES_GCM_authenticated_decryption_test_case_1 succeeded + TestCase [17] : test_AES_GCM_authenticated_decryption_test_case_2 succeeded + TestCase [18] : test_AES_GCM_authenticated_decryption_test_case_3 succeeded + TestCase [19] : test_AES_GCM_authenticated_decryption_test_case_4 succeeded + TestCase [20] : test_AES_GCM_authenticated_decryption_test_case_5 succeeded + TestCase [21] : test_AES_GCM_authenticated_decryption_test_case_6 succeeded + TestCase [22] : test_AES_GCM_authenticated_decryption_test_case_7 succeeded + TestCase [23] : test_AES_GCM_auth_encryption_test_case_192_1 succeeded + TestCase [24] : test_AES_GCM_auth_encryption_test_case_192_2 succeeded + TestCase [25] : test_AES_GCM_auth_encryption_test_case_192_3 succeeded + TestCase [26] : test_AES_GCM_auth_encryption_test_case_192_4 succeeded + TestCase [27] : test_AES_GCM_auth_encryption_test_case_192_5 succeeded + TestCase [28] : test_AES_GCM_auth_encryption_test_case_192_6 succeeded + TestCase [29] : test_AES_GCM_auth_encryption_test_case_192_7 succeeded + TestCase [30] : test_AES_GCM_auth_decryption_test_case_192_1 succeeded + TestCase [31] : test_AES_GCM_auth_decryption_test_case_192_2 succeeded + TestCase [32] : test_AES_GCM_auth_decryption_test_case_192_3 succeeded + TestCase [33] : test_AES_GCM_auth_decryption_test_case_192_4 succeeded + TestCase [34] : test_AES_GCM_auth_decryption_test_case_192_5 succeeded + TestCase [35] : test_AES_GCM_auth_decryption_test_case_192_6 succeeded + TestCase [36] : test_AES_GCM_auth_decryption_test_case_192_7 succeeded + TestCase [37] : test_AES_GCM_auth_encryption_test_case_256_1 succeeded + TestCase [38] : test_AES_GCM_auth_encryption_test_case_256_2 succeeded + TestCase [39] : test_AES_GCM_auth_encryption_test_case_256_3 succeeded + TestCase [40] : test_AES_GCM_auth_encryption_test_case_256_4 succeeded + TestCase [41] : test_AES_GCM_auth_encryption_test_case_256_5 succeeded + TestCase [42] : test_AES_GCM_auth_encryption_test_case_256_6 succeeded + TestCase [43] : test_AES_GCM_auth_encryption_test_case_256_7 succeeded + TestCase [44] : test_AES_GCM_auth_decryption_test_case_256_1 succeeded + TestCase [45] : test_AES_GCM_auth_decryption_test_case_256_2 succeeded + TestCase [46] : test_AES_GCM_auth_decryption_test_case_256_3 succeeded + TestCase [47] : test_AES_GCM_auth_decryption_test_case_256_4 succeeded + TestCase [48] : test_AES_GCM_auth_decryption_test_case_256_5 succeeded + TestCase [49] : test_AES_GCM_auth_decryption_test_case_256_6 succeeded + TestCase [50] : test_AES_GCM_auth_decryption_test_case_256_7 succeeded + TestCase [51] : test_AES_GMAC_authentication_test_case_1 succeeded + TestCase [52] : test_AES_GMAC_authentication_verify_test_case_1 succeeded + TestCase [53] : test_AES_GMAC_authentication_test_case_2 succeeded + TestCase [54] : test_AES_GMAC_authentication_verify_test_case_2 succeeded + TestCase [55] : test_AES_GMAC_authentication_test_case_3 succeeded + TestCase [56] : test_AES_GMAC_authentication_verify_test_case_3 succeeded + TestCase [57] : test_AES_GMAC_authentication_test_case_4 succeeded + TestCase [58] : test_AES_GMAC_authentication_verify_test_case_4 succeeded + TestCase [59] : test_AES_CCM_authenticated_encryption_test_case_128_1 succeeded + TestCase [60] : test_AES_CCM_authenticated_encryption_test_case_128_2 succeeded + TestCase [61] : test_AES_CCM_authenticated_encryption_test_case_128_3 succeeded + TestCase [62] : test_AES_CCM_authenticated_decryption_test_case_128_1 succeeded + TestCase [63] : test_AES_CCM_authenticated_decryption_test_case_128_2 succeeded + TestCase [64] : test_AES_CCM_authenticated_decryption_test_case_128_3 succeeded + TestCase [65] : test_AES_CCM_authenticated_encryption_test_case_192_1 succeeded + TestCase [66] : test_AES_CCM_authenticated_encryption_test_case_192_2 succeeded + TestCase [67] : test_AES_CCM_authenticated_encryption_test_case_192_3 succeeded + TestCase [68] : test_AES_CCM_authenticated_decryption_test_case_192_1 succeeded + TestCase [69] : test_AES_CCM_authenticated_decryption_test_case_192_2 succeeded + TestCase [70] : test_AES_CCM_authenticated_decryption_test_case_192_3 succeeded + TestCase [71] : test_AES_CCM_authenticated_encryption_test_case_256_1 succeeded + TestCase [72] : test_AES_CCM_authenticated_encryption_test_case_256_2 succeeded + TestCase [73] : test_AES_CCM_authenticated_encryption_test_case_256_3 succeeded + TestCase [74] : test_AES_CCM_authenticated_decryption_test_case_256_1 succeeded + TestCase [75] : test_AES_CCM_authenticated_decryption_test_case_256_2 succeeded + TestCase [76] : test_AES_CCM_authenticated_decryption_test_case_256_3 succeeded + TestCase [77] : test_AES_GCM_auth_encrypt_SGL_out_of_place_400B_1seg succeeded + TestCase [78] : authentication_verify_HMAC_SHA1_fail_data_corrupt succeeded + TestCase [79] : authentication_verify_HMAC_SHA1_fail_tag_corrupt succeeded + TestCase [80] : authentication_verify_AES128_GMAC_fail_data_corrupt succeeded + TestCase [81] : authentication_verify_AES128_GMAC_fail_tag_corrupt succeeded + TestCase [82] : auth_decryption_AES128CBC_HMAC_SHA1_fail_data_corrupt succeeded + TestCase [83] : auth_decryption_AES128CBC_HMAC_SHA1_fail_tag_corrupt succeeded + ------------------------------------------------------- + + Test Suite Summary + Tests Total : 84 + Tests Skipped : 0 + Tests Executed : 84 + Tests Unsupported: 0 + Tests Passed : 84 + Tests Failed : 0 + ------------------------------------------------------- + Test OK RTE>>cryptodev_null_autotest + ------------------------------------------------------- + + Test Suite : Crypto Device NULL Unit Test Suite CRYPTODEV: [crypto_null] - Creating cryptodev crypto_null CRYPTODEV: [crypto_null] - Initialisation parameters - name: crypto_null,socket id: 1, max queue pairs: 8, max sessions: 2048 + ------------------------------------------------------- + + TestCase [ 0] : test_null_auth_only_operation succeeded + TestCase [ 1] : test_null_cipher_only_operation succeeded + TestCase [ 2] : test_null_cipher_auth_operation succeeded + TestCase [ 3] : test_null_auth_cipher_operation succeeded CRYPTODEV: [crypto_null] null_crypto_pmd_session_configure() line 323: failed configure session parameters CRYPTODEV: rte_cryptodev_sym_session_init() line 1111: dev_id 1 failed to configure session details CRYPTODEV: [crypto_null] null_crypto_pmd_session_configure() line 323: failed configure session parameters CRYPTODEV: rte_cryptodev_sym_session_init() line 1111: dev_id 1 failed to configure session details + TestCase [ 4] : test_null_invalid_operation succeeded + TestCase [ 5] : test_null_burst_operation succeeded + ------------------------------------------------------- + + Test Suite Summary + Tests Total : 6 + Tests Skipped : 0 + Tests Executed : 6 + Tests Unsupported: 0 + Tests Passed : 6 + Tests Failed : 0 + ------------------------------------------------------- + Test OK RTE>> 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 -ugen -----Original Message----- From: Trahe, Fiona [mailto:fiona.trahe@intel.com] Sent: 27 April 2018 16:01 To: Kudupudi, Ugendreshwar <Ugendreshwar.Kudupudi@cavium.com>; users@dpdk.org Subject: RE: OpenSSL Crypto PMD Fails Have you tried the unit tests? make test-build cd build/build/test/test /test -l1 -n1 > cryptodev_openssl_autotest > cryptodev_null_autotest > -----Original Message----- > From: Kudupudi, Ugendreshwar [mailto:Ugendreshwar.Kudupudi@cavium.com] > Sent: Friday, April 27, 2018 11:24 AM > To: Trahe, Fiona <fiona.trahe@intel.com>; users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > Yes. I did. > > # Compile PMD for Software backed device > CONFIG_RTE_LIBRTE_PMD_OPENSSL=y CONFIG_RTE_LIBRTE_PMD_OPENSSL_DEBUG=n > > -ugen > > -----Original Message----- > From: Trahe, Fiona [mailto:fiona.trahe@intel.com] > Sent: 27 April 2018 15:49 > To: Kudupudi, Ugendreshwar <Ugendreshwar.Kudupudi@cavium.com>; > users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > 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 > > :1 > > 1: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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] OpenSSL Crypto PMD Fails 2018-04-30 11:22 ` Kudupudi, Ugendreshwar @ 2018-05-04 10:09 ` Kudupudi, Ugendreshwar 2018-05-08 9:58 ` Trahe, Fiona 0 siblings, 1 reply; 7+ messages in thread From: Kudupudi, Ugendreshwar @ 2018-05-04 10:09 UTC (permalink / raw) To: Trahe, Fiona, users Hello Fiona After some digging in the code and correcting the command arguments, I got it working. The example given in the dpdk documentation should be corrected. 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 --cipher_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 -ugen -----Original Message----- From: Kudupudi, Ugendreshwar Sent: 30 April 2018 16:52 To: 'Trahe, Fiona' <fiona.trahe@intel.com>; users@dpdk.org Subject: RE: OpenSSL Crypto PMD Fails Following is the log of autotest and l2fwd-crypto. RTE>>cryptodev_openssl_autotest + ------------------------------------------------------- + + Test Suite : Crypto Device OPENSSL Unit Test Suite + ------------------------------------------------------- + + TestCase [ 0] : test_multi_session succeeded + TestCase [ 1] : test_multi_session_random_usage succeeded 0) TestCase AES-128-CTR HMAC-SHA1 Encryption Digest PASS 1) TestCase AES-128-CTR HMAC-SHA1 Decryption Digest Verify PASS 2) TestCase AES-256-CTR HMAC-SHA1 Encryption Digest PASS 3) TestCase AES-256-CTR HMAC-SHA1 Decryption Digest Verify PASS 4) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest PASS 5) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest Scatter Gather PASS 6) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify PASS 7) TestCase AES-128-CBC HMAC-SHA256 Encryption Digest PASS 8) TestCase AES-128-CBC HMAC-SHA256 Decryption Digest Verify PASS 9) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest PASS 10) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest Sessionless PASS 11) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest Scatter Gather Sessionless PASS 12) TestCase AES-128-CBC HMAC-SHA512 Decryption Digest Verify PASS 13) TestCase AES-128-CBC HMAC-SHA512 Decryption Digest Verify Scatter Gather PASS 14) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest OOP PASS 15) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify OOP PASS 16) TestCase AES-128-CBC HMAC-SHA224 Encryption Digest PASS 17) TestCase AES-128-CBC HMAC-SHA224 Decryption Digest Verify PASS 18) TestCase AES-128-CBC HMAC-SHA384 Encryption Digest PASS 19) TestCase AES-128-CBC HMAC-SHA384 Decryption Digest Verify PASS 20) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest Sessionless PASS 21) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify Sessionless PASS + TestCase [ 2] : test_AES_chain_openssl_all succeeded 0) TestCase AES-128-CBC Encryption PASS 1) TestCase AES-128-CBC Decryption PASS 2) TestCase AES-192-CBC Encryption PASS 3) TestCase AES-192-CBC Encryption Scater gather PASS 4) TestCase AES-192-CBC Decryption PASS 5) TestCase AES-256-CBC Encryption PASS 6) TestCase AES-256-CBC Decryption PASS 7) TestCase AES-256-CBC OOP Encryption PASS 8) TestCase AES-256-CBC OOP Decryption PASS 9) TestCase AES-128-CTR Encryption PASS 10) TestCase AES-128-CTR Decryption PASS 11) TestCase AES-192-CTR Encryption PASS 12) TestCase AES-192-CTR Decryption PASS 13) TestCase AES-256-CTR Encryption PASS 14) TestCase AES-256-CTR Decryption PASS + TestCase [ 3] : test_AES_cipheronly_openssl_all succeeded 0) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest PASS 1) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify PASS 2) TestCase 3DES-128-CBC SHA1 Encryption Digest PASS 3) TestCase 3DES-128-CBC SHA1 Decryption Digest Verify PASS 4) TestCase 3DES-192-CBC HMAC-SHA1 Encryption Digest PASS 5) TestCase 3DES-192-CBC HMAC-SHA1 Decryption Digest Verify PASS 6) TestCase 3DES-192-CBC SHA1 Encryption Digest PASS 7) TestCase 3DES-192-CBC SHA1 Decryption Digest Verify PASS 8) TestCase 3DES-128-CTR HMAC-SHA1 Encryption Digest PASS 9) TestCase 3DES-128-CTR HMAC-SHA1 Decryption Digest Verify PASS 10) TestCase 3DES-128-CTR SHA1 Encryption Digest PASS 11) TestCase 3DES-128-CTR SHA1 Decryption Digest Verify PASS 12) TestCase 3DES-192-CTR HMAC-SHA1 Encryption Digest PASS 13) TestCase 3DES-192-CTR HMAC-SHA1 Decryption Digest Verify PASS 14) TestCase 3DES-192-CTR SHA1 Encryption Digest PASS 15) TestCase 3DES-192-CTR SHA1 Decryption Digest Verify PASS 16) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest OOP PASS 17) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify OOP PASS 18) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest Sessionless PASS 19) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify Sessionless PASS + TestCase [ 4] : test_3DES_chain_openssl_all succeeded 0) TestCase 3DES-128-CBC Encryption PASS 1) TestCase 3DES-128-CBC Decryption PASS 2) TestCase 3DES-192-CBC Encryption PASS 3) TestCase 3DES-192-CBC Decryption PASS 4) TestCase 3DES-128-CTR Encryption PASS 5) TestCase 3DES-128-CTR Decryption PASS 6) TestCase 3DES-192-CTR Encryption PASS 7) TestCase 3DES-192-CTR Decryption PASS + TestCase [ 5] : test_3DES_cipheronly_openssl_all succeeded 0) TestCase DES-CBC Encryption PASS 1) TestCase DES-CBC Decryption PASS + TestCase [ 6] : test_DES_cipheronly_openssl_all succeeded 0) TestCase DES-DOCSIS-BPI Full Block Encryption PASS 1) TestCase DES-DOCSIS-BPI Runt Block Encryption PASS 2) TestCase DES-DOCSIS-BPI Uneven Encryption PASS 3) TestCase DES-DOCSIS-BPI Full Block Decryption PASS 4) TestCase DES-DOCSIS-BPI Runt Block Decryption PASS 5) TestCase DES-DOCSIS-BPI Uneven Decryption PASS 6) TestCase DES-DOCSIS-BPI OOP Full Block Encryption PASS 7) TestCase DES-DOCSIS-BPI OOP Runt Block Encryption PASS 8) TestCase DES-DOCSIS-BPI OOP Uneven Encryption PASS 9) TestCase DES-DOCSIS-BPI OOP Full Block Decryption PASS 10) TestCase DES-DOCSIS-BPI OOP Runt Block Decryption PASS 11) TestCase DES-DOCSIS-BPI OOP Uneven Decryption PASS + TestCase [ 7] : test_DES_docsis_openssl_all succeeded 0) TestCase MD5 Digest PASS 1) TestCase MD5 Digest Verify PASS 2) TestCase HMAC-MD5 Digest PASS 3) TestCase HMAC-MD5 Digest Verify PASS 4) TestCase SHA1 Digest PASS 5) TestCase SHA1 Digest Verify PASS 6) TestCase HMAC-SHA1 Digest PASS 7) TestCase HMAC-SHA1 Digest Verify PASS 8) TestCase SHA224 Digest PASS 9) TestCase SHA224 Digest Verify PASS 10) TestCase HMAC-SHA224 Digest PASS 11) TestCase HMAC-SHA224 Digest Verify PASS 12) TestCase SHA256 Digest PASS 13) TestCase SHA256 Digest Verify PASS 14) TestCase HMAC-SHA256 Digest PASS 15) TestCase HMAC-SHA256 Digest Verify PASS 16) TestCase SHA384 Digest PASS 17) TestCase SHA384 Digest Verify PASS 18) TestCase HMAC-SHA384 Digest PASS 19) TestCase HMAC-SHA384 Digest Verify PASS 20) TestCase SHA512 Digest PASS 21) TestCase SHA512 Digest Verify PASS 22) TestCase HMAC-SHA512 Digest PASS 23) TestCase HMAC-SHA512 Digest Verify PASS + TestCase [ 8] : test_authonly_openssl_all succeeded + TestCase [ 9] : test_AES_GCM_authenticated_encryption_test_case_1 succeeded + TestCase [10] : test_AES_GCM_authenticated_encryption_test_case_2 succeeded + TestCase [11] : test_AES_GCM_authenticated_encryption_test_case_3 succeeded + TestCase [12] : test_AES_GCM_authenticated_encryption_test_case_4 succeeded + TestCase [13] : test_AES_GCM_authenticated_encryption_test_case_5 succeeded + TestCase [14] : test_AES_GCM_authenticated_encryption_test_case_6 succeeded + TestCase [15] : test_AES_GCM_authenticated_encryption_test_case_7 succeeded + TestCase [16] : test_AES_GCM_authenticated_decryption_test_case_1 succeeded + TestCase [17] : test_AES_GCM_authenticated_decryption_test_case_2 succeeded + TestCase [18] : test_AES_GCM_authenticated_decryption_test_case_3 succeeded + TestCase [19] : test_AES_GCM_authenticated_decryption_test_case_4 succeeded + TestCase [20] : test_AES_GCM_authenticated_decryption_test_case_5 succeeded + TestCase [21] : test_AES_GCM_authenticated_decryption_test_case_6 succeeded + TestCase [22] : test_AES_GCM_authenticated_decryption_test_case_7 succeeded + TestCase [23] : test_AES_GCM_auth_encryption_test_case_192_1 succeeded + TestCase [24] : test_AES_GCM_auth_encryption_test_case_192_2 succeeded + TestCase [25] : test_AES_GCM_auth_encryption_test_case_192_3 succeeded + TestCase [26] : test_AES_GCM_auth_encryption_test_case_192_4 succeeded + TestCase [27] : test_AES_GCM_auth_encryption_test_case_192_5 succeeded + TestCase [28] : test_AES_GCM_auth_encryption_test_case_192_6 succeeded + TestCase [29] : test_AES_GCM_auth_encryption_test_case_192_7 succeeded + TestCase [30] : test_AES_GCM_auth_decryption_test_case_192_1 succeeded + TestCase [31] : test_AES_GCM_auth_decryption_test_case_192_2 succeeded + TestCase [32] : test_AES_GCM_auth_decryption_test_case_192_3 succeeded + TestCase [33] : test_AES_GCM_auth_decryption_test_case_192_4 succeeded + TestCase [34] : test_AES_GCM_auth_decryption_test_case_192_5 succeeded + TestCase [35] : test_AES_GCM_auth_decryption_test_case_192_6 succeeded + TestCase [36] : test_AES_GCM_auth_decryption_test_case_192_7 succeeded + TestCase [37] : test_AES_GCM_auth_encryption_test_case_256_1 succeeded + TestCase [38] : test_AES_GCM_auth_encryption_test_case_256_2 succeeded + TestCase [39] : test_AES_GCM_auth_encryption_test_case_256_3 succeeded + TestCase [40] : test_AES_GCM_auth_encryption_test_case_256_4 succeeded + TestCase [41] : test_AES_GCM_auth_encryption_test_case_256_5 succeeded + TestCase [42] : test_AES_GCM_auth_encryption_test_case_256_6 succeeded + TestCase [43] : test_AES_GCM_auth_encryption_test_case_256_7 succeeded + TestCase [44] : test_AES_GCM_auth_decryption_test_case_256_1 succeeded + TestCase [45] : test_AES_GCM_auth_decryption_test_case_256_2 succeeded + TestCase [46] : test_AES_GCM_auth_decryption_test_case_256_3 succeeded + TestCase [47] : test_AES_GCM_auth_decryption_test_case_256_4 succeeded + TestCase [48] : test_AES_GCM_auth_decryption_test_case_256_5 succeeded + TestCase [49] : test_AES_GCM_auth_decryption_test_case_256_6 succeeded + TestCase [50] : test_AES_GCM_auth_decryption_test_case_256_7 succeeded + TestCase [51] : test_AES_GMAC_authentication_test_case_1 succeeded + TestCase [52] : test_AES_GMAC_authentication_verify_test_case_1 succeeded + TestCase [53] : test_AES_GMAC_authentication_test_case_2 succeeded + TestCase [54] : test_AES_GMAC_authentication_verify_test_case_2 succeeded + TestCase [55] : test_AES_GMAC_authentication_test_case_3 succeeded + TestCase [56] : test_AES_GMAC_authentication_verify_test_case_3 succeeded + TestCase [57] : test_AES_GMAC_authentication_test_case_4 succeeded + TestCase [58] : test_AES_GMAC_authentication_verify_test_case_4 succeeded + TestCase [59] : test_AES_CCM_authenticated_encryption_test_case_128_1 succeeded + TestCase [60] : test_AES_CCM_authenticated_encryption_test_case_128_2 succeeded + TestCase [61] : test_AES_CCM_authenticated_encryption_test_case_128_3 succeeded + TestCase [62] : test_AES_CCM_authenticated_decryption_test_case_128_1 succeeded + TestCase [63] : test_AES_CCM_authenticated_decryption_test_case_128_2 succeeded + TestCase [64] : test_AES_CCM_authenticated_decryption_test_case_128_3 succeeded + TestCase [65] : test_AES_CCM_authenticated_encryption_test_case_192_1 succeeded + TestCase [66] : test_AES_CCM_authenticated_encryption_test_case_192_2 succeeded + TestCase [67] : test_AES_CCM_authenticated_encryption_test_case_192_3 succeeded + TestCase [68] : test_AES_CCM_authenticated_decryption_test_case_192_1 succeeded + TestCase [69] : test_AES_CCM_authenticated_decryption_test_case_192_2 succeeded + TestCase [70] : test_AES_CCM_authenticated_decryption_test_case_192_3 succeeded + TestCase [71] : test_AES_CCM_authenticated_encryption_test_case_256_1 succeeded + TestCase [72] : test_AES_CCM_authenticated_encryption_test_case_256_2 succeeded + TestCase [73] : test_AES_CCM_authenticated_encryption_test_case_256_3 succeeded + TestCase [74] : test_AES_CCM_authenticated_decryption_test_case_256_1 succeeded + TestCase [75] : test_AES_CCM_authenticated_decryption_test_case_256_2 succeeded + TestCase [76] : test_AES_CCM_authenticated_decryption_test_case_256_3 succeeded + TestCase [77] : test_AES_GCM_auth_encrypt_SGL_out_of_place_400B_1seg succeeded + TestCase [78] : authentication_verify_HMAC_SHA1_fail_data_corrupt succeeded + TestCase [79] : authentication_verify_HMAC_SHA1_fail_tag_corrupt succeeded + TestCase [80] : authentication_verify_AES128_GMAC_fail_data_corrupt succeeded + TestCase [81] : authentication_verify_AES128_GMAC_fail_tag_corrupt succeeded + TestCase [82] : auth_decryption_AES128CBC_HMAC_SHA1_fail_data_corrupt succeeded + TestCase [83] : auth_decryption_AES128CBC_HMAC_SHA1_fail_tag_corrupt succeeded + ------------------------------------------------------- + + Test Suite Summary + Tests Total : 84 + Tests Skipped : 0 + Tests Executed : 84 + Tests Unsupported: 0 + Tests Passed : 84 + Tests Failed : 0 + ------------------------------------------------------- + Test OK RTE>>cryptodev_null_autotest + ------------------------------------------------------- + + Test Suite : Crypto Device NULL Unit Test Suite CRYPTODEV: [crypto_null] - Creating cryptodev crypto_null CRYPTODEV: [crypto_null] - Initialisation parameters - name: crypto_null,socket id: 1, max queue pairs: 8, max sessions: 2048 + ------------------------------------------------------- + + TestCase [ 0] : test_null_auth_only_operation succeeded + TestCase [ 1] : test_null_cipher_only_operation succeeded + TestCase [ 2] : test_null_cipher_auth_operation succeeded + TestCase [ 3] : test_null_auth_cipher_operation succeeded CRYPTODEV: [crypto_null] null_crypto_pmd_session_configure() line 323: failed configure session parameters CRYPTODEV: rte_cryptodev_sym_session_init() line 1111: dev_id 1 failed to configure session details CRYPTODEV: [crypto_null] null_crypto_pmd_session_configure() line 323: failed configure session parameters CRYPTODEV: rte_cryptodev_sym_session_init() line 1111: dev_id 1 failed to configure session details + TestCase [ 4] : test_null_invalid_operation succeeded + TestCase [ 5] : test_null_burst_operation succeeded + ------------------------------------------------------- + + Test Suite Summary + Tests Total : 6 + Tests Skipped : 0 + Tests Executed : 6 + Tests Unsupported: 0 + Tests Passed : 6 + Tests Failed : 0 + ------------------------------------------------------- + Test OK RTE>> 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 -ugen -----Original Message----- From: Trahe, Fiona [mailto:fiona.trahe@intel.com] Sent: 27 April 2018 16:01 To: Kudupudi, Ugendreshwar <Ugendreshwar.Kudupudi@cavium.com>; users@dpdk.org Subject: RE: OpenSSL Crypto PMD Fails Have you tried the unit tests? make test-build cd build/build/test/test /test -l1 -n1 > cryptodev_openssl_autotest > cryptodev_null_autotest > -----Original Message----- > From: Kudupudi, Ugendreshwar [mailto:Ugendreshwar.Kudupudi@cavium.com] > Sent: Friday, April 27, 2018 11:24 AM > To: Trahe, Fiona <fiona.trahe@intel.com>; users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > Yes. I did. > > # Compile PMD for Software backed device > CONFIG_RTE_LIBRTE_PMD_OPENSSL=y CONFIG_RTE_LIBRTE_PMD_OPENSSL_DEBUG=n > > -ugen > > -----Original Message----- > From: Trahe, Fiona [mailto:fiona.trahe@intel.com] > Sent: 27 April 2018 15:49 > To: Kudupudi, Ugendreshwar <Ugendreshwar.Kudupudi@cavium.com>; > users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > 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 > > :1 > > 1: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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [dpdk-users] OpenSSL Crypto PMD Fails 2018-05-04 10:09 ` Kudupudi, Ugendreshwar @ 2018-05-08 9:58 ` Trahe, Fiona 0 siblings, 0 replies; 7+ messages in thread From: Trahe, Fiona @ 2018-05-08 9:58 UTC (permalink / raw) To: Kudupudi, Ugendreshwar, users > -----Original Message----- > From: Kudupudi, Ugendreshwar [mailto:Ugendreshwar.Kudupudi@cavium.com] > Sent: Friday, May 4, 2018 11:09 AM > To: Trahe, Fiona <fiona.trahe@intel.com>; users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > Hello Fiona > > After some digging in the code and correcting the command arguments, I got it working. The example > given in the dpdk documentation should be corrected. [Fiona] It would be great if you could push a patch to update the documentation. > > 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 --cipher_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 > > -ugen > > -----Original Message----- > From: Kudupudi, Ugendreshwar > Sent: 30 April 2018 16:52 > To: 'Trahe, Fiona' <fiona.trahe@intel.com>; users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > Following is the log of autotest and l2fwd-crypto. > > RTE>>cryptodev_openssl_autotest > + ------------------------------------------------------- + + Test Suite : Crypto Device OPENSSL Unit Test Suite + --------- > ---------------------------------------------- + + TestCase [ 0] : test_multi_session succeeded + TestCase [ 1] : > test_multi_session_random_usage succeeded > 0) TestCase AES-128-CTR HMAC-SHA1 Encryption Digest PASS > 1) TestCase AES-128-CTR HMAC-SHA1 Decryption Digest Verify PASS > 2) TestCase AES-256-CTR HMAC-SHA1 Encryption Digest PASS > 3) TestCase AES-256-CTR HMAC-SHA1 Decryption Digest Verify PASS > 4) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest PASS > 5) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest Scatter Gather PASS > 6) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify PASS > 7) TestCase AES-128-CBC HMAC-SHA256 Encryption Digest PASS > 8) TestCase AES-128-CBC HMAC-SHA256 Decryption Digest Verify PASS > 9) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest PASS > 10) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest Sessionless PASS > 11) TestCase AES-128-CBC HMAC-SHA512 Encryption Digest Scatter Gather Sessionless PASS > 12) TestCase AES-128-CBC HMAC-SHA512 Decryption Digest Verify PASS > 13) TestCase AES-128-CBC HMAC-SHA512 Decryption Digest Verify Scatter Gather PASS > 14) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest OOP PASS > 15) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify OOP PASS > 16) TestCase AES-128-CBC HMAC-SHA224 Encryption Digest PASS > 17) TestCase AES-128-CBC HMAC-SHA224 Decryption Digest Verify PASS > 18) TestCase AES-128-CBC HMAC-SHA384 Encryption Digest PASS > 19) TestCase AES-128-CBC HMAC-SHA384 Decryption Digest Verify PASS > 20) TestCase AES-128-CBC HMAC-SHA1 Encryption Digest Sessionless PASS > 21) TestCase AES-128-CBC HMAC-SHA1 Decryption Digest Verify Sessionless PASS + TestCase [ 2] : > test_AES_chain_openssl_all succeeded > 0) TestCase AES-128-CBC Encryption PASS > 1) TestCase AES-128-CBC Decryption PASS > 2) TestCase AES-192-CBC Encryption PASS > 3) TestCase AES-192-CBC Encryption Scater gather PASS > 4) TestCase AES-192-CBC Decryption PASS > 5) TestCase AES-256-CBC Encryption PASS > 6) TestCase AES-256-CBC Decryption PASS > 7) TestCase AES-256-CBC OOP Encryption PASS > 8) TestCase AES-256-CBC OOP Decryption PASS > 9) TestCase AES-128-CTR Encryption PASS > 10) TestCase AES-128-CTR Decryption PASS > 11) TestCase AES-192-CTR Encryption PASS > 12) TestCase AES-192-CTR Decryption PASS > 13) TestCase AES-256-CTR Encryption PASS > 14) TestCase AES-256-CTR Decryption PASS + TestCase [ 3] : test_AES_cipheronly_openssl_all succeeded > 0) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest PASS > 1) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify PASS > 2) TestCase 3DES-128-CBC SHA1 Encryption Digest PASS > 3) TestCase 3DES-128-CBC SHA1 Decryption Digest Verify PASS > 4) TestCase 3DES-192-CBC HMAC-SHA1 Encryption Digest PASS > 5) TestCase 3DES-192-CBC HMAC-SHA1 Decryption Digest Verify PASS > 6) TestCase 3DES-192-CBC SHA1 Encryption Digest PASS > 7) TestCase 3DES-192-CBC SHA1 Decryption Digest Verify PASS > 8) TestCase 3DES-128-CTR HMAC-SHA1 Encryption Digest PASS > 9) TestCase 3DES-128-CTR HMAC-SHA1 Decryption Digest Verify PASS > 10) TestCase 3DES-128-CTR SHA1 Encryption Digest PASS > 11) TestCase 3DES-128-CTR SHA1 Decryption Digest Verify PASS > 12) TestCase 3DES-192-CTR HMAC-SHA1 Encryption Digest PASS > 13) TestCase 3DES-192-CTR HMAC-SHA1 Decryption Digest Verify PASS > 14) TestCase 3DES-192-CTR SHA1 Encryption Digest PASS > 15) TestCase 3DES-192-CTR SHA1 Decryption Digest Verify PASS > 16) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest OOP PASS > 17) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify OOP PASS > 18) TestCase 3DES-128-CBC HMAC-SHA1 Encryption Digest Sessionless PASS > 19) TestCase 3DES-128-CBC HMAC-SHA1 Decryption Digest Verify Sessionless PASS + TestCase [ 4] : > test_3DES_chain_openssl_all succeeded > 0) TestCase 3DES-128-CBC Encryption PASS > 1) TestCase 3DES-128-CBC Decryption PASS > 2) TestCase 3DES-192-CBC Encryption PASS > 3) TestCase 3DES-192-CBC Decryption PASS > 4) TestCase 3DES-128-CTR Encryption PASS > 5) TestCase 3DES-128-CTR Decryption PASS > 6) TestCase 3DES-192-CTR Encryption PASS > 7) TestCase 3DES-192-CTR Decryption PASS + TestCase [ 5] : test_3DES_cipheronly_openssl_all > succeeded > 0) TestCase DES-CBC Encryption PASS > 1) TestCase DES-CBC Decryption PASS > + TestCase [ 6] : test_DES_cipheronly_openssl_all succeeded > 0) TestCase DES-DOCSIS-BPI Full Block Encryption PASS > 1) TestCase DES-DOCSIS-BPI Runt Block Encryption PASS > 2) TestCase DES-DOCSIS-BPI Uneven Encryption PASS > 3) TestCase DES-DOCSIS-BPI Full Block Decryption PASS > 4) TestCase DES-DOCSIS-BPI Runt Block Decryption PASS > 5) TestCase DES-DOCSIS-BPI Uneven Decryption PASS > 6) TestCase DES-DOCSIS-BPI OOP Full Block Encryption PASS > 7) TestCase DES-DOCSIS-BPI OOP Runt Block Encryption PASS > 8) TestCase DES-DOCSIS-BPI OOP Uneven Encryption PASS > 9) TestCase DES-DOCSIS-BPI OOP Full Block Decryption PASS > 10) TestCase DES-DOCSIS-BPI OOP Runt Block Decryption PASS > 11) TestCase DES-DOCSIS-BPI OOP Uneven Decryption PASS + TestCase [ 7] : test_DES_docsis_openssl_all > succeeded > 0) TestCase MD5 Digest PASS > 1) TestCase MD5 Digest Verify PASS > 2) TestCase HMAC-MD5 Digest PASS > 3) TestCase HMAC-MD5 Digest Verify PASS > 4) TestCase SHA1 Digest PASS > 5) TestCase SHA1 Digest Verify PASS > 6) TestCase HMAC-SHA1 Digest PASS > 7) TestCase HMAC-SHA1 Digest Verify PASS > 8) TestCase SHA224 Digest PASS > 9) TestCase SHA224 Digest Verify PASS > 10) TestCase HMAC-SHA224 Digest PASS > 11) TestCase HMAC-SHA224 Digest Verify PASS > 12) TestCase SHA256 Digest PASS > 13) TestCase SHA256 Digest Verify PASS > 14) TestCase HMAC-SHA256 Digest PASS > 15) TestCase HMAC-SHA256 Digest Verify PASS > 16) TestCase SHA384 Digest PASS > 17) TestCase SHA384 Digest Verify PASS > 18) TestCase HMAC-SHA384 Digest PASS > 19) TestCase HMAC-SHA384 Digest Verify PASS > 20) TestCase SHA512 Digest PASS > 21) TestCase SHA512 Digest Verify PASS > 22) TestCase HMAC-SHA512 Digest PASS > 23) TestCase HMAC-SHA512 Digest Verify PASS + TestCase [ 8] : test_authonly_openssl_all succeeded + > TestCase [ 9] : test_AES_GCM_authenticated_encryption_test_case_1 succeeded + TestCase [10] : > test_AES_GCM_authenticated_encryption_test_case_2 succeeded + TestCase [11] : > test_AES_GCM_authenticated_encryption_test_case_3 succeeded + TestCase [12] : > test_AES_GCM_authenticated_encryption_test_case_4 succeeded + TestCase [13] : > test_AES_GCM_authenticated_encryption_test_case_5 succeeded + TestCase [14] : > test_AES_GCM_authenticated_encryption_test_case_6 succeeded + TestCase [15] : > test_AES_GCM_authenticated_encryption_test_case_7 succeeded + TestCase [16] : > test_AES_GCM_authenticated_decryption_test_case_1 succeeded + TestCase [17] : > test_AES_GCM_authenticated_decryption_test_case_2 succeeded + TestCase [18] : > test_AES_GCM_authenticated_decryption_test_case_3 succeeded + TestCase [19] : > test_AES_GCM_authenticated_decryption_test_case_4 succeeded + TestCase [20] : > test_AES_GCM_authenticated_decryption_test_case_5 succeeded + TestCase [21] : > test_AES_GCM_authenticated_decryption_test_case_6 succeeded + TestCase [22] : > test_AES_GCM_authenticated_decryption_test_case_7 succeeded + TestCase [23] : > test_AES_GCM_auth_encryption_test_case_192_1 succeeded + TestCase [24] : > test_AES_GCM_auth_encryption_test_case_192_2 succeeded + TestCase [25] : > test_AES_GCM_auth_encryption_test_case_192_3 succeeded + TestCase [26] : > test_AES_GCM_auth_encryption_test_case_192_4 succeeded + TestCase [27] : > test_AES_GCM_auth_encryption_test_case_192_5 succeeded + TestCase [28] : > test_AES_GCM_auth_encryption_test_case_192_6 succeeded + TestCase [29] : > test_AES_GCM_auth_encryption_test_case_192_7 succeeded + TestCase [30] : > test_AES_GCM_auth_decryption_test_case_192_1 succeeded + TestCase [31] : > test_AES_GCM_auth_decryption_test_case_192_2 succeeded + TestCase [32] : > test_AES_GCM_auth_decryption_test_case_192_3 succeeded + TestCase [33] : > test_AES_GCM_auth_decryption_test_case_192_4 succeeded + TestCase [34] : > test_AES_GCM_auth_decryption_test_case_192_5 succeeded + TestCase [35] : > test_AES_GCM_auth_decryption_test_case_192_6 succeeded + TestCase [36] : > test_AES_GCM_auth_decryption_test_case_192_7 succeeded + TestCase [37] : > test_AES_GCM_auth_encryption_test_case_256_1 succeeded + TestCase [38] : > test_AES_GCM_auth_encryption_test_case_256_2 succeeded + TestCase [39] : > test_AES_GCM_auth_encryption_test_case_256_3 succeeded + TestCase [40] : > test_AES_GCM_auth_encryption_test_case_256_4 succeeded + TestCase [41] : > test_AES_GCM_auth_encryption_test_case_256_5 succeeded + TestCase [42] : > test_AES_GCM_auth_encryption_test_case_256_6 succeeded + TestCase [43] : > test_AES_GCM_auth_encryption_test_case_256_7 succeeded + TestCase [44] : > test_AES_GCM_auth_decryption_test_case_256_1 succeeded + TestCase [45] : > test_AES_GCM_auth_decryption_test_case_256_2 succeeded + TestCase [46] : > test_AES_GCM_auth_decryption_test_case_256_3 succeeded + TestCase [47] : > test_AES_GCM_auth_decryption_test_case_256_4 succeeded + TestCase [48] : > test_AES_GCM_auth_decryption_test_case_256_5 succeeded + TestCase [49] : > test_AES_GCM_auth_decryption_test_case_256_6 succeeded + TestCase [50] : > test_AES_GCM_auth_decryption_test_case_256_7 succeeded + TestCase [51] : > test_AES_GMAC_authentication_test_case_1 succeeded + TestCase [52] : > test_AES_GMAC_authentication_verify_test_case_1 succeeded + TestCase [53] : > test_AES_GMAC_authentication_test_case_2 succeeded + TestCase [54] : > test_AES_GMAC_authentication_verify_test_case_2 succeeded + TestCase [55] : > test_AES_GMAC_authentication_test_case_3 succeeded + TestCase [56] : > test_AES_GMAC_authentication_verify_test_case_3 succeeded + TestCase [57] : > test_AES_GMAC_authentication_test_case_4 succeeded + TestCase [58] : > test_AES_GMAC_authentication_verify_test_case_4 succeeded + TestCase [59] : > test_AES_CCM_authenticated_encryption_test_case_128_1 succeeded + TestCase [60] : > test_AES_CCM_authenticated_encryption_test_case_128_2 succeeded + TestCase [61] : > test_AES_CCM_authenticated_encryption_test_case_128_3 succeeded + TestCase [62] : > test_AES_CCM_authenticated_decryption_test_case_128_1 succeeded + TestCase [63] : > test_AES_CCM_authenticated_decryption_test_case_128_2 succeeded + TestCase [64] : > test_AES_CCM_authenticated_decryption_test_case_128_3 succeeded + TestCase [65] : > test_AES_CCM_authenticated_encryption_test_case_192_1 succeeded + TestCase [66] : > test_AES_CCM_authenticated_encryption_test_case_192_2 succeeded + TestCase [67] : > test_AES_CCM_authenticated_encryption_test_case_192_3 succeeded + TestCase [68] : > test_AES_CCM_authenticated_decryption_test_case_192_1 succeeded + TestCase [69] : > test_AES_CCM_authenticated_decryption_test_case_192_2 succeeded + TestCase [70] : > test_AES_CCM_authenticated_decryption_test_case_192_3 succeeded + TestCase [71] : > test_AES_CCM_authenticated_encryption_test_case_256_1 succeeded + TestCase [72] : > test_AES_CCM_authenticated_encryption_test_case_256_2 succeeded + TestCase [73] : > test_AES_CCM_authenticated_encryption_test_case_256_3 succeeded + TestCase [74] : > test_AES_CCM_authenticated_decryption_test_case_256_1 succeeded + TestCase [75] : > test_AES_CCM_authenticated_decryption_test_case_256_2 succeeded + TestCase [76] : > test_AES_CCM_authenticated_decryption_test_case_256_3 succeeded + TestCase [77] : > test_AES_GCM_auth_encrypt_SGL_out_of_place_400B_1seg succeeded + TestCase [78] : > authentication_verify_HMAC_SHA1_fail_data_corrupt succeeded + TestCase [79] : > authentication_verify_HMAC_SHA1_fail_tag_corrupt succeeded + TestCase [80] : > authentication_verify_AES128_GMAC_fail_data_corrupt succeeded + TestCase [81] : > authentication_verify_AES128_GMAC_fail_tag_corrupt succeeded + TestCase [82] : > auth_decryption_AES128CBC_HMAC_SHA1_fail_data_corrupt succeeded + TestCase [83] : > auth_decryption_AES128CBC_HMAC_SHA1_fail_tag_corrupt succeeded + ------------------------------------------- > ------------ + + Test Suite Summary > + Tests Total : 84 > + Tests Skipped : 0 > + Tests Executed : 84 > + Tests Unsupported: 0 > + Tests Passed : 84 > + Tests Failed : 0 > + ------------------------------------------------------- + Test OK > RTE>>cryptodev_null_autotest > + ------------------------------------------------------- + + Test Suite : Crypto Device NULL Unit Test Suite > CRYPTODEV: [crypto_null] - Creating cryptodev crypto_null > > CRYPTODEV: [crypto_null] - Initialisation parameters - name: crypto_null,socket id: 1, max queue pairs: 8, > max sessions: 2048 + ------------------------------------------------------- + + TestCase [ 0] : > test_null_auth_only_operation succeeded + TestCase [ 1] : test_null_cipher_only_operation succeeded + > TestCase [ 2] : test_null_cipher_auth_operation succeeded + TestCase [ 3] : > test_null_auth_cipher_operation succeeded > CRYPTODEV: [crypto_null] null_crypto_pmd_session_configure() line 323: failed configure session > parameters > CRYPTODEV: rte_cryptodev_sym_session_init() line 1111: dev_id 1 failed to configure session details > CRYPTODEV: [crypto_null] null_crypto_pmd_session_configure() line 323: failed configure session > parameters > CRYPTODEV: rte_cryptodev_sym_session_init() line 1111: dev_id 1 failed to configure session details + > TestCase [ 4] : test_null_invalid_operation succeeded + TestCase [ 5] : test_null_burst_operation > succeeded + ------------------------------------------------------- + + Test Suite Summary > + Tests Total : 6 > + Tests Skipped : 0 > + Tests Executed : 6 > + Tests Unsupported: 0 > + Tests Passed : 6 > + Tests Failed : 0 > + ------------------------------------------------------- + Test OK > RTE>> > > 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 > > -ugen > > -----Original Message----- > From: Trahe, Fiona [mailto:fiona.trahe@intel.com] > Sent: 27 April 2018 16:01 > To: Kudupudi, Ugendreshwar <Ugendreshwar.Kudupudi@cavium.com>; users@dpdk.org > Subject: RE: OpenSSL Crypto PMD Fails > > Have you tried the unit tests? > make test-build > cd build/build/test/test > /test -l1 -n1 > > cryptodev_openssl_autotest > > cryptodev_null_autotest > > > > -----Original Message----- > > From: Kudupudi, Ugendreshwar [mailto:Ugendreshwar.Kudupudi@cavium.com] > > Sent: Friday, April 27, 2018 11:24 AM > > To: Trahe, Fiona <fiona.trahe@intel.com>; users@dpdk.org > > Subject: RE: OpenSSL Crypto PMD Fails > > > > Yes. I did. > > > > # Compile PMD for Software backed device > > CONFIG_RTE_LIBRTE_PMD_OPENSSL=y CONFIG_RTE_LIBRTE_PMD_OPENSSL_DEBUG=n > > > > -ugen > > > > -----Original Message----- > > From: Trahe, Fiona [mailto:fiona.trahe@intel.com] > > Sent: 27 April 2018 15:49 > > To: Kudupudi, Ugendreshwar <Ugendreshwar.Kudupudi@cavium.com>; > > users@dpdk.org > > Subject: RE: OpenSSL Crypto PMD Fails > > > > 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 > > > :1 > > > 1: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 ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2018-05-08 9:58 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-04-25 13:23 [dpdk-users] OpenSSL Crypto PMD Fails Kudupudi, Ugendreshwar 2018-04-27 10:19 ` Trahe, Fiona 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
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).