DPDK patches and discussions
 help / color / mirror / Atom feed
From: <amartya.das@wipro.com>
To: <anupam.kapoor@gmail.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [Crypto-API query]
Date: Tue, 28 Jun 2016 07:01:02 +0000	[thread overview]
Message-ID: <PS1PR03MB1883AA6829954054C8E07461ED220@PS1PR03MB1883.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <87furxon3k.fsf@fatcat.parallelwireless>

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

      reply	other threads:[~2016-06-28  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  5:27 amartya.das
2016-06-28  5:51 ` Anupam Kapoor
2016-06-28  6:09   ` amartya.das
2016-06-28  6:15     ` Anupam Kapoor
2016-06-28  7:01       ` amartya.das [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PS1PR03MB1883AA6829954054C8E07461ED220@PS1PR03MB1883.apcprd03.prod.outlook.com \
    --to=amartya.das@wipro.com \
    --cc=anupam.kapoor@gmail.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).