From: Felipe Polanco <felipeapolanco@gmail.com>
To: users@dpdk.org
Subject: Assistance needed to enable ipsec mb on dpdk
Date: Wed, 31 May 2023 11:17:21 -0400 [thread overview]
Message-ID: <CADcj3=6i7ct_uvP=HqzV_G7+qL2pBu6rWLrg8H4wvb-MWdPtLg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1599 bytes --]
Hi,
We have two identical servers with dpdk and ipsecMB libraries installed.
One of the servers was configured by a colleague and its working fine with
dpdk-test-crypto-perf but I'm configuring the other and is failing with
cannot find cryptodev device
1st server OK:
CRYPTODEV: Creating cryptodev crypto_aesni_gcm
CRYPTODEV: Initialisation parameters - name: crypto_aesni_gcm,socket id: 0,
max queue pairs: 8
ipsec_mb_create() line 168: IPSec Multi-buffer library version used: 1.3.0
TELEMETRY: No legacy callbacks, legacy socket not created
Allocated pool "sess_mp_0" on socket 0
lcore id Buf Size Burst Size Enqueued Dequeued Failed Enq
Failed Deq MOps Gbps Cycles/Buf
1 1500 32 300000 300000 0
0 6.2472 74.9660 336.15
2nd server NOK:
CRYPTODEV: Creating cryptodev crypto_aesni_gcm
CRYPTODEV: Initialisation parameters - name: crypto_aesni_gcm,socket id: 0,
max queue pairs: 8
CRYPTODEV: rte_cryptodev_pmd_create() line 115: Failed to allocate crypto
device for crypto_aesni_gcm
ipsec_mb_create() line 118: driver : create failed
vdev_probe(): failed to initialize crypto_aesni_gcm device
EAL: Bus (vdev) probe failed.
TELEMETRY: No legacy callbacks, legacy socket not created
No crypto devices type crypto_aesni_gcm available
USER1: Failed to initialise requested crypto device type
Steps I'm performing:
Installing IPSECMB from
https://github.com/intel/intel-ipsec-mb
Compiling dpdk-stable-22.11.1 and installing it.
Anything else I need to do to in order to enable IPSECMB on DPDK?
[-- Attachment #2: Type: text/html, Size: 2083 bytes --]
reply other threads:[~2023-06-05 15:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CADcj3=6i7ct_uvP=HqzV_G7+qL2pBu6rWLrg8H4wvb-MWdPtLg@mail.gmail.com' \
--to=felipeapolanco@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).