DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 42] Crypto_mrvl error with multiple instances
Date: Wed, 09 May 2018 07:40:11 +0000	[thread overview]
Message-ID: <bug-42-3@http.dpdk.org/tracker/> (raw)

https://dpdk.org/tracker/show_bug.cgi?id=42

            Bug ID: 42
           Summary: Crypto_mrvl error with multiple instances
           Product: DPDK
           Version: unspecified
          Hardware: ARM
                OS: Linux
            Status: CONFIRMED
          Severity: major
          Priority: Normal
         Component: cryptodev
          Assignee: dev@dpdk.org
          Reporter: akhil.gupta@puresoftware.com
  Target Milestone: ---

Hi,
We are using DPDK over Marvell ARMADA 8040 processor and we have used all the
MUSDK patches provided, to make our DPDK stack work.

But we are facing an issue while trying to use L2FWD-Crypto test application.
Here we are trying to use crypto_mrvl with two instances and we are getting
error on second one.
The command used is:
./l2fwd-crypto  -c 0x3 -n 4 --vdev=net_ring,iface=eth1,iface=eth0
--vdev=crypto_mrvl0 --vdev=crypto_mrvl1 -- \
  --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

While executing this, we are getting the errors:
[ERROR] Engine #0: Ring #0 is busy. Active rings map is 0x1
Failed to setup queue pair 0 on cryptodev 1EAL: Error - exiting with code: 1
  Cause: Failed to initialize crypto devices 


Can you please let us know if you see any issue is above command line being
used.
In addition, can we use multiple instances for single crypto engine supported
by Armada 8040?

Regards,
Akhil

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-05-09  7:40 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=bug-42-3@http.dpdk.org/tracker/ \
    --to=bugzilla@dpdk.org \
    --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).