From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Dirk-Holger Lenz <dirk.lenz@ng4t.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] cannot allocate more than one vdev device of a type
Date: Thu, 3 Aug 2017 13:57:59 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBE824D@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <933d585b-6e5e-f032-040f-2f99bab733ff@ng4t.com>
Hi Dirk,
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Dirk-Holger
> Lenz
> Sent: Thursday, August 3, 2017 2:46 PM
> To: users@dpdk.org
> Subject: [dpdk-users] cannot allocate more than one vdev device of a type
>
> it is not possible to allocate more than one vdev of a type
>
> (e.g. crypto_openssl or crypto_aesni_mb).
You should use different suffixes when using a same crypto driver:
i.e. --vdev "crypto_openssl1" --vdev "crypto_openssl2".
Regards,
Pablo
next prev parent reply other threads:[~2017-08-03 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 13:45 Dirk-Holger Lenz
2017-08-03 13:57 ` De Lara Guarch, Pablo [this message]
2017-08-03 14:09 ` Dirk-Holger Lenz
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=E115CCD9D858EF4F90C690B0DCB4D8976CBE824D@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dirk.lenz@ng4t.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).