[dpdk-users] crypto device 'crypto_aesni_mb' doesn't work in secondary process

De Lara Guarch, Pablo pablo.de.lara.guarch at intel.com
Fri Aug 4 11:37:26 CEST 2017

Hi Dirk,

> -----Original Message-----
> From: users [mailto:users-bounces at dpdk.org] On Behalf Of Dirk-Holger
> Lenz
> Sent: Friday, August 4, 2017 9:14 AM
> To: users at dpdk.org
> Subject: [dpdk-users] crypto device 'crypto_aesni_mb' doesn't work in
> secondary process
> when the crypto device of type 'crypto_aesni_mb' is
> created in the primary process a secondary process
> crashes when writing into the encryption queue.
> The dequeue function rte_cryptodev_dequeue_burst()
> crashes in flush_mb_mgr() when it tries to access the
> structure of function pointers qp->op_fns.
> The reason is that this structure is allocated by the
> primary process in its memory which is not accessible
> in the secondary process (of course also the function
> pointers are pointing to code of the primary process).

Virtual devices have to be initialized in both processes,
as they cannot be shared between them.


More information about the users mailing list