[dpdk-dev] [Crypto-API query]

[dpdk-dev] [Crypto-API query]

[amartya.das]

Hi,

Is it possible to use Crypto API with virtual device without VFIO and by using UIO only.

Thanks,
Amartya
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

Re: [dpdk-dev] [Crypto-API query]

[Anupam Kapoor]

>>>>> [2016-06-28T10:57:02+0530]: "amartya.das" (amartya.das):
,----[ amartya.das ]
| Is it possible to use Crypto API with virtual device without VFIO and by using UIO only.
`----
i have just taken a cursory look at the l2fwd-crypto, and it seems it is
possible to have sw-only crypto devices...

---
thanks
anupam

Re: [dpdk-dev] [Crypto-API query]

[amartya.das]

Hi,

Thanks for the prompt response.

I am trying to run one sample application with crypto library with DPDK 16.04 from below path in VM:
dpdk-16.04/examples/l2fwd-crypto

I have followed below link:
http://dpdk.org/doc/guides-16.04/cryptodevs/aesni_mb.html

Command use:
./build/l2fwd-crypto -c 0x1 -n 4 --vdev "cryptodev_aesni_mb_pmd" --vdev "cryptodev_aesni_mb_pmd" -- -p 0x1 --chain CIPHER_HASH --cipher_op ENCRYPT --cipher_algo AES_CBC --cipher_key 00:01:02:03:04:05:06:07:08:09:0a:0b:0c:0d:0e:0f --auth_op GENERATE --auth_algo SHA1_HMAC --auth_key 10:11:12:13:14:15:16:17:18:19:1a:1b:1c:1d:1e:1f

I am getting below error:
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 1 lcore(s)
EAL: Probing VFIO support...
EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or directory)
EAL: VFIO modules not loaded, skipping VFIO support...
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x1e00000 bytes
EAL: Virtual area found at 0x7fa6bd200000 (size = 0x1e00000)
EAL: Ask a virtual area of 0x3e200000 bytes
EAL: Virtual area found at 0x7fa67ee00000 (size = 0x3e200000)
EAL: Ask a virtual area of 0x3fc00000 bytes
EAL: Virtual area found at 0x7fa63f000000 (size = 0x3fc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fa63ec00000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fa63e800000 (size = 0x200000)
EAL: Requesting 1024 pages of size 2MB from socket 0
EAL: TSC frequency is ~1995189 KHz
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
EAL: Master lcore 0 is ready (tid=c11ca8c0;cpuset=[0])
EAL: no driver found for cryptodev_aesni_mb_pmd
EAL: failed to initialize cryptodev_aesni_mb_pmd device
PANIC in rte_eal_init():
Cannot init pmd devices
6: [./build/l2fwd-crypto() [0x42e0a3]]
5: [/lib64/libc.so.6(__libc_start_main+0xf0) [0x7fa6c02ebfe0]]
4: [./build/l2fwd-crypto(main+0x2f) [0x42b2cf]]
3: [./build/l2fwd-crypto(rte_eal_init+0xdc0) [0x49f920]]
2: [./build/l2fwd-crypto(__rte_panic+0xc9) [0x425008]]
1: [./build/l2fwd-crypto(rte_dump_stack+0x18) [0x4a6748]]
Aborted (core dumped)

What could be cause for driver not found? And init fails?

Thanks,
Amartya


-----Original Message-----
From: Anupam Kapoor [mailto:anupam.kapoor@gmail.com]
Sent: Tuesday, June 28, 2016 11:21 AM
To: Amartya Kumar Das (MFG & Tech) <amartya.das@wipro.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [Crypto-API query]

** This mail has been sent from an external source **

>>>>> [2016-06-28T10:57:02+0530]: "amartya.das" (amartya.das):
,----[ amartya.das ]
| Is it possible to use Crypto API with virtual device without VFIO and by using UIO only.
`----
i have just taken a cursory look at the l2fwd-crypto, and it seems it is possible to have sw-only crypto devices...

---
thanks
anupam
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

Re: [dpdk-dev] [Crypto-API query]

[Anupam Kapoor]

>>>>> [2016-06-28T11:39:08+0530]: "amartya.das" (amartya.das):

,----[ amartya.das ]
| EAL: no driver found for cryptodev_aesni_mb_pmd
| EAL: failed to initialize cryptodev_aesni_mb_pmd device
`----
i have a _hunch_ that you have might have missed building the
multi-buffer-crypto-pmd...

for more information take a look here:
http://dpdk.readthedocs.io/en/v16.04/cryptodevs/index.html

--
thanks
anupam

Re: [dpdk-dev] [Crypto-API query]

[amartya.das]

It did compiled by make YASM=/usr/bin/yasm for in /home/test/ipsec_043/code:


Making object file obj/gcm_avx_gen4.o
/usr/bin/yasm -f x64 -f elf64 -X gnu -g dwarf2 -D LINUX -D __linux__ -I include -I . avx2/gcm_avx_gen4.asm -o obj/gcm_avx_gen4.o
--------------------------------------------------------------
ar -qcs libIPSec_MB.a obj/aes128_cbc_dec_by4_sse.o obj/aes128_cbc_dec_by8_avx.o obj/aes128_cntr_by4_sse.o obj/aes128_cntr_by8_avx.o obj/aes128_ecbenc_x3.o obj/aes192_cbc_dec_by4_sse.o obj/aes192_cbc_dec_by8_avx.o obj/aes192_cntr_by4_sse.o obj/aes192_cntr_by8_avx.o obj/aes256_cbc_dec_by4_sse.o obj/aes256_cbc_dec_by8_avx.o obj/aes256_cntr_by4_sse.o obj/aes256_cntr_by8_avx.o obj/aes_cbc_enc_128_x4.o obj/aes_cbc_enc_128_x8.o obj/aes_cbc_enc_192_x4.o obj/aes_cbc_enc_192_x8.o obj/aes_cbc_enc_256_x4.o obj/aes_cbc_enc_256_x8.o obj/aes_keyexp_128.o obj/aes_keyexp_192.o obj/aes_keyexp_256.o obj/aes_xcbc_mac_128_x4.o obj/aes_xcbc_mac_128_x8.o obj/mb_mgr_aes192_flush_avx.o obj/mb_mgr_aes192_flush_sse.o obj/mb_mgr_aes192_submit_avx.o obj/mb_mgr_aes192_submit_sse.o obj/mb_mgr_aes256_flush_avx.o obj/mb_mgr_aes256_flush_sse.o obj/mb_mgr_aes256_submit_avx.o obj/mb_mgr_aes256_submit_sse.o obj/mb_mgr_aes_flush_avx.o obj/mb_mgr_aes_flush_sse.o obj/mb_mgr_aes_submit_avx.o obj/mb_mgr_aes_submit_sse.o obj/mb_mgr_aes_xcbc_flush_avx.o obj/mb_mgr_aes_xcbc_flush_sse.o obj/mb_mgr_aes_xcbc_submit_avx.o obj/mb_mgr_aes_xcbc_submit_sse.o obj/mb_mgr_hmac_flush_avx.o obj/mb_mgr_hmac_flush_avx2.o obj/mb_mgr_hmac_flush_sse.o obj/mb_mgr_hmac_md5_flush_avx.o obj/mb_mgr_hmac_md5_flush_avx2.o obj/mb_mgr_hmac_md5_flush_sse.o obj/mb_mgr_hmac_md5_submit_avx.o obj/mb_mgr_hmac_md5_submit_avx2.o obj/mb_mgr_hmac_md5_submit_sse.o obj/mb_mgr_hmac_sha_224_flush_avx.o obj/mb_mgr_hmac_sha_224_flush_avx2.o obj/mb_mgr_hmac_sha_224_flush_sse.o obj/mb_mgr_hmac_sha_224_submit_avx.o obj/mb_mgr_hmac_sha_224_submit_avx2.o obj/mb_mgr_hmac_sha_224_submit_sse.o obj/mb_mgr_hmac_sha_256_flush_avx.o obj/mb_mgr_hmac_sha_256_flush_avx2.o obj/mb_mgr_hmac_sha_256_flush_sse.o obj/mb_mgr_hmac_sha_256_submit_avx.o obj/mb_mgr_hmac_sha_256_submit_avx2.o obj/mb_mgr_hmac_sha_256_submit_sse.o obj/mb_mgr_hmac_sha_384_flush_avx.o obj/mb_mgr_hmac_sha_384_flush_avx2.o obj/mb_mgr_hmac_sha_384_flush_sse.o obj/mb_mgr_hmac_sha_384_submit_avx.o obj/mb_mgr_hmac_sha_384_submit_avx2.o obj/mb_mgr_hmac_sha_384_submit_sse.o obj/mb_mgr_hmac_sha_512_flush_avx.o obj/mb_mgr_hmac_sha_512_flush_avx2.o obj/mb_mgr_hmac_sha_512_flush_sse.o obj/mb_mgr_hmac_sha_512_submit_avx.o obj/mb_mgr_hmac_sha_512_submit_avx2.o obj/mb_mgr_hmac_sha_512_submit_sse.o obj/mb_mgr_hmac_submit_avx.o obj/mb_mgr_hmac_submit_avx2.o obj/mb_mgr_hmac_submit_sse.o obj/md5_x4x2_avx.o obj/md5_x4x2_sse.o obj/md5_x8x2_avx2.o obj/save_xmms.o obj/sha1_mult_avx.o obj/sha1_mult_sse.o obj/sha1_one_block_avx.o obj/sha1_one_block_sse.o obj/sha1_x8_avx2.o obj/sha224_one_block_avx.o obj/sha224_one_block_sse.o obj/sha256_oct_avx2.o obj/sha256_one_block_avx.o obj/sha256_one_block_sse.o obj/sha384_one_block_avx.o obj/sha384_one_block_sse.o obj/sha512_one_block_avx.o obj/sha512_one_block_sse.o obj/sha512_x2_avx.o obj/sha512_x2_sse.o obj/sha512_x4_avx2.o obj/sha_256_mult_avx.o obj/sha_256_mult_sse.o obj/aes_xcbc_expand_key.o obj/mb_mgr_avx.o obj/mb_mgr_avx2.o obj/mb_mgr_sse.o obj/md5_one_block.o obj/gcm_sse.o obj/gcm_avx_gen2.o obj/gcm_avx_gen4.o


Next,
export AESNI_MULTI_BUFFER_LIB_PATH=/home/test/ipsec_043/code

and

 CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y in config/common_base done.

Then I was trying to run from by ./l2fwd-crypto -c 40 -n 4 --vdev="cryptodev_aesni_mb_pmd,socket_id=1,max_nb_sessions=128" from below path:

/home/test/dpdk-16.04/examples/l2fwd-crypto/build

But getting same error:

EAL: Detected lcore 0 as core 0 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 1 lcore(s)
EAL: Probing VFIO support...
EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or directory)
EAL: VFIO modules not loaded, skipping VFIO support...
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x1e00000 bytes
EAL: Virtual area found at 0x7f944a800000 (size = 0x1e00000)
EAL: Ask a virtual area of 0x3e200000 bytes
EAL: Virtual area found at 0x7f940c400000 (size = 0x3e200000)
EAL: Ask a virtual area of 0x3fc00000 bytes
EAL: Virtual area found at 0x7f93cc600000 (size = 0x3fc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f93cc200000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f93cbe00000 (size = 0x200000)
EAL: Requesting 1024 pages of size 2MB from socket 0
EAL: TSC frequency is ~1995194 KHz
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
EAL: Master lcore 0 is ready (tid=4e8d18c0;cpuset=[0])
EAL: no driver found for cryptodev_aesni_mb_pmd
EAL: failed to initialize cryptodev_aesni_mb_pmd device
PANIC in rte_eal_init():
Cannot init pmd devices
6: [./l2fwd-crypto() [0x42e0a3]]
5: [/lib64/libc.so.6(__libc_start_main+0xf0) [0x7f944d9f2fe0]]
4: [./l2fwd-crypto(main+0x2f) [0x42b2cf]]
3: [./l2fwd-crypto(rte_eal_init+0xdc0) [0x49f920]]
2: [./l2fwd-crypto(__rte_panic+0xc9) [0x425008]]
1: [./l2fwd-crypto(rte_dump_stack+0x18) [0x4a6748]]
Aborted (core dumped)


Not sure about the problem, any path setting wrong so that it is not fetching?

Thanks,
Amartya

-----Original Message-----
From: Anupam Kapoor [mailto:anupam.kapoor@gmail.com]
Sent: Tuesday, June 28, 2016 11:46 AM
To: Amartya Kumar Das (MFG & Tech) <amartya.das@wipro.com>
Cc: anupam.kapoor@gmail.com; dev@dpdk.org
Subject: Re: [dpdk-dev] [Crypto-API query]

** This mail has been sent from an external source **

>>>>> [2016-06-28T11:39:08+0530]: "amartya.das" (amartya.das):

,----[ amartya.das ]
| EAL: no driver found for cryptodev_aesni_mb_pmd
| EAL: failed to initialize cryptodev_aesni_mb_pmd device
`----
i have a _hunch_ that you have might have missed building the multi-buffer-crypto-pmd...

for more information take a look here:
http://dpdk.readthedocs.io/en/v16.04/cryptodevs/index.html

--
thanks
anupam
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com