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] crypto device 'crypto_aesni_mb' doesn't work in secondary process
Date: Fri, 4 Aug 2017 09:37:26 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CBE8BFF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <3c73733b-6fe0-7480-9443-0a9f1610400d@ng4t.com>
Hi Dirk,
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Dirk-Holger
> Lenz
> Sent: Friday, August 4, 2017 9:14 AM
> To: users@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.
Thanks,
Pablo
next prev parent reply other threads:[~2017-08-04 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 8:14 Dirk-Holger Lenz
2017-08-04 9:37 ` De Lara Guarch, Pablo [this message]
2017-08-04 9:56 ` Dirk-Holger Lenz
2017-08-04 10:11 ` 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=E115CCD9D858EF4F90C690B0DCB4D8976CBE8BFF@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).