From: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
To: Ali Hmaity <ali.hmaity@polimi.it>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Problems running l2fwd-crypto in DPDK release 17-11
Date: Sat, 2 Dec 2017 12:24:11 +0500 [thread overview]
Message-ID: <CAN7yQ2przGnz3Cqnz9MCfigtQC-ksXgMdF8Vzu64tNWrJ=gwGA@mail.gmail.com> (raw)
In-Reply-To: <CAN7yQ2rMggQVH2+mXbVBMjM-tKqNDo6O4AKHz-FpSj6LZU2gvQ@mail.gmail.com>
Hello you are using 16.04 are u sure the version is compatible?
On Dec 1, 2017 5:21 PM, "Ali Hmaity" <ali.hmaity@polimi.it> wrote:
Hello,
I am encoutring issues to run the l2fwd.crypto sample application. I
followed the tutorial step by step, but still not able to run the
application. In detail, this is what I did:
1.downloded ip-sec from https://github.com/01org/
intel-ipsec-mb/archive/v0.47.zip
2. Extracted it
3. export ESNI_MULTI_BUFFER_LIB_PATH='pwd'
4. make
5in the /build/.config i set CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y
6. build DPDK again with the following commands:
export RTE_SDK=<location of DPDK source code>/dpdk-16.04
export DESTDIR=<location where I want DPDK to install>/install"
export RTE_TARGET=x86_64-native-linuxapp-gcc
make clean install
7. Binded the crypto device to igb_uio module ( I also tries all the steps
without this one)
8. build l2fwd-crypto application
9. run the application with the following commands:
/l2fwd-crypto -l 1,2 -n 4 --vdev="crypto_aesni_mb,
socket_id=0,max_nb_sessions=128" -- -p 0x3 --cdev SW --chain CIPHER_HASH
--cipher_algo "aes-cbc" --auth_algo "sha1-hmac"
It doesn't work. The output says: Unable to parse device "crypto_aesni_mb".
I am running ubuntu 16.04 LTS with kernel 4.10.0-40-generic.
Can you please help?
____________________
Ali Hmaity, Ph.D student
Dept. of Electronics, Information and Bioengineering
phone: (+39) 02 2399 3489
E-mail: ali.hmaity@polimi.it
Web page: <http://home.deib.polimi.it/fmusumeci>
http://www.deib.polimi.it/ita/personale/details/644298
prev parent reply other threads:[~2017-12-02 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 12:21 Ali Hmaity
[not found] ` <CAN7yQ2qmU+JQGDfWDwAv1Tftk01BZ=Zw=3eLKo8_Xn4FYKimpQ@mail.gmail.com>
[not found] ` <CAN7yQ2rMggQVH2+mXbVBMjM-tKqNDo6O4AKHz-FpSj6LZU2gvQ@mail.gmail.com>
2017-12-02 7:24 ` Muhammad Zain-ul-Abideen [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='CAN7yQ2przGnz3Cqnz9MCfigtQC-ksXgMdF8Vzu64tNWrJ=gwGA@mail.gmail.com' \
--to=zain2294@gmail.com \
--cc=ali.hmaity@polimi.it \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).