DPDK usage discussions
 help / color / mirror / Atom feed
From: "Doherty, Declan" <declan.doherty@intel.com>
To: "Das, Surajit" <Surajit.Das@commscope.com>,
	"users@dpdk.org" <users@dpdk.org>
Cc: "Dharwadkar, Sriram" <Sriram.Dharwadkar@commscope.com>
Subject: Re: [dpdk-users] Using l2fwd-crypto sample app
Date: Wed, 20 Jan 2021 17:28:59 +0000
Message-ID: <ee6c178d-c149-2590-cf90-a6a65761bb2f@intel.com> (raw)
In-Reply-To: <SN6PR14MB2253D55DC9786CDB12223BFFE9AE0@SN6PR14MB2253.namprd14.prod.outlook.com>

Hey Surajit,

It's difficult to tell from the log output but have you actually 
installed the required libraries for the IPsec MB PMD on your system. If 
you're not sure look at the installation guide in the documentation:

If your interested in IPsec, you could also have a look at our IPsec 
Security Gateway sample application, which implements most of the data 
path of an IPsec security gateway, see the docs here 
http://doc.dpdk.org/guides/sample_app_ug/ipsec_secgw.html for details


On 08/01/2021 9:08 AM, Das, Surajit wrote:
> Hi DPDK Experts,
> We are working on expanding our DPDK application to do IPSec based encryption.
> To that end I was trying out the sample application provided.
> But, I am hitting an error which is probably configuration related.
> My DPDK version:
> dpdk-stable-19.11.5
> OS: CentOS Linux release 7.7.1908 (Core)
> Kernel: 3.10.0-1062.el7.x86_64
> Command run with options and output:
> ./l2fwd-crypto -l 0-1 -n 4 --vdev "crypto_aesni_mb0" --vdev "crypto_aesni_mb1" -- -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 --auth_op GENERATE --auth_algo aes-xcbc-mac --auth_key 10:11:12:13:14:15:16:17:18:19:1a:1b:1c:1d:1e:1f
> EAL: Detected 8 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: failed to parse device "crypto_aesni_mb0"
> EAL: Unable to parse device 'crypto_aesni_mb0'
> EAL: Error - exiting with code: 1
>    Cause: Invalid EAL arguments
> I am not sure what is causing the error failed to parse device "crypto_aesni_mb0"
> Is there a specific driver that needs to be loaded? Or is there a hardware dependency?
> I am using virtio nic to test out the app.
> Please suggest if the info I have provided is sufficient to determine the cause?
> NIC and driver details:
> Network devices using DPDK-compatible driver
> ============================================
> 0000:00:04.0 'Virtio network device 1000' drv=uio_pci_generic unused=virtio_pci
> 0000:00:05.0 'Virtio network device 1000' drv=uio_pci_generic unused=virtio_pci
> 0000:00:06.0 'Virtio network device 1000' drv=uio_pci_generic unused=virtio_pci
> 0000:00:07.0 'Virtio network device 1000' drv=uio_pci_generic unused=virtio_pci
> 00:04.0 Ethernet controller: Red Hat, Inc. Virtio network device
>       Subsystem: Red Hat, Inc. Device 0001
>       Physical Slot: 4
>       Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
>       Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>       Interrupt: pin A routed to IRQ 11
>       Region 0: I/O ports at c060 [size=32]
>       Region 1: Memory at febd2000 (32-bit, non-prefetchable) [size=4K]
>       Expansion ROM at feac0000 [disabled] [size=256K]
>       Capabilities: [40] MSI-X: Enable- Count=3 Masked-
>             Vector table: BAR=1 offset=00000000
>             PBA: BAR=1 offset=00000800
>       Kernel driver in use: uio_pci_generic
>       Kernel modules: virtio_pci
> Processor details:
> Architecture:          x86_64
> CPU op-mode(s):        32-bit, 64-bit
> Byte Order:            Little Endian
> CPU(s):                8
> On-line CPU(s) list:   0-7
> Thread(s) per core:    1
> Core(s) per socket:    8
> Socket(s):             1
> NUMA node(s):          1
> Vendor ID:             GenuineIntel
> CPU family:            6
> Model:                 44
> Model name:            Westmere E56xx/L56xx/X56xx (Nehalem-C)
> Stepping:              1
> CPU MHz:               2693.676
> BogoMIPS:              5387.35
> Hypervisor vendor:     KVM
> Virtualization type:   full
> L1d cache:             32K
> L1i cache:             32K
> L2 cache:              4096K
> NUMA node0 CPU(s):     0-7
> Flags:                 fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx lm constant_tsc rep_good nopl eagerfpu pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes hypervisor lahf_lm md_clear
> Regards,
> Surajit

  parent reply	other threads:[~2021-01-20 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08  9:08 Das, Surajit
2021-01-10 21:00 ` Das, Surajit
2021-01-20 17:28 ` Doherty, Declan [this message]
2021-01-21 16:11   ` Das, Surajit

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:

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

  git send-email \
    --in-reply-to=ee6c178d-c149-2590-cf90-a6a65761bb2f@intel.com \
    --to=declan.doherty@intel.com \
    --cc=Sriram.Dharwadkar@commscope.com \
    --cc=Surajit.Das@commscope.com \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git