DPDK usage discussions
 help / color / mirror / Atom feed
From: Dirk-Holger Lenz <dirk.lenz@ng4t.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] crypto device 'crypto_aesni_mb' doesn't work in secondary process
Date: Fri, 4 Aug 2017 10:14:13 +0200	[thread overview]
Message-ID: <3c73733b-6fe0-7480-9443-0a9f1610400d@ng4t.com> (raw)

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

             reply	other threads:[~2017-08-04  8:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04  8:14 Dirk-Holger Lenz [this message]
2017-08-04  9:37 ` De Lara Guarch, Pablo
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=3c73733b-6fe0-7480-9443-0a9f1610400d@ng4t.com \
    --to=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).