DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] cannot allocate more than one vdev device of a type
@ 2017-08-03 13:45 Dirk-Holger Lenz
  2017-08-03 13:57 ` De Lara Guarch, Pablo
  0 siblings, 1 reply; 3+ messages in thread
From: Dirk-Holger Lenz @ 2017-08-03 13:45 UTC (permalink / raw)
  To: users

it is not possible to allocate more than one vdev of a type

(e.g. crypto_openssl or crypto_aesni_mb).

Our application may use several crypto devices which may

be virtual devices.

In the past it was possible to have several arguments of

--vdev (as much as devices needed)

(e.g. --vdev=crypto_openssl) given to rte_eal_init().

In the current version (17.08rc3) in any case only one device

is allocated.

In our case we are using dpdk built as shared libraries.

This happens due to the check in vdev_scan():

         dev = find_vdev(devargs->name);
         if (dev)
             continue;

and in rte_cryptodev_pmd_allocate()

     if (rte_cryptodev_pmd_get_named_dev(name) != NULL) {
         CDEV_LOG_ERR("Crypto device with name %s already "
                 "allocated!", name);
         return NULL;
     }

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-users] cannot allocate more than one vdev device of a type
  2017-08-03 13:45 [dpdk-users] cannot allocate more than one vdev device of a type Dirk-Holger Lenz
@ 2017-08-03 13:57 ` De Lara Guarch, Pablo
  2017-08-03 14:09   ` Dirk-Holger Lenz
  0 siblings, 1 reply; 3+ messages in thread
From: De Lara Guarch, Pablo @ 2017-08-03 13:57 UTC (permalink / raw)
  To: Dirk-Holger Lenz, users

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-users] cannot allocate more than one vdev device of a type
  2017-08-03 13:57 ` De Lara Guarch, Pablo
@ 2017-08-03 14:09   ` Dirk-Holger Lenz
  0 siblings, 0 replies; 3+ messages in thread
From: Dirk-Holger Lenz @ 2017-08-03 14:09 UTC (permalink / raw)
  To: De Lara Guarch, Pablo, users

Hi Pablo,
thanks a lot, this works :-).
Regards
Dirk

On 08/03/2017 03:57 PM, De Lara Guarch, Pablo wrote:
> 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-08-03 14:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-08-03 13:45 [dpdk-users] cannot allocate more than one vdev device of a type Dirk-Holger Lenz
2017-08-03 13:57 ` De Lara Guarch, Pablo
2017-08-03 14:09   ` Dirk-Holger Lenz

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).