DPDK usage discussions
 help / color / mirror / Atom feed
From: Dirk-Holger Lenz <dirk.lenz@ng4t.com>
To: users@dpdk.org
Subject: [dpdk-users] If shared libraries are used vdev doesn't work anymore
Date: Mon, 31 Jul 2017 16:58:17 +0200	[thread overview]
Message-ID: <9fb283ed-223d-713e-4722-21278f4cfd6e@ng4t.com> (raw)

If dpdk is built with 'CONFIG_RTE_BUILD_SHARED_LIB=y' then
using the vdev feature (args: e.g. -c 3 -n 4 --vdev="crypto_openssl")
the rte_eal_init() returns 'ERROR: failed to parse device "crypto_openssl"'.
It looks to me that rte_eal_devargs_add() calling rte_eal_devargs_parse()
is trying to check the device name before the shared libraries are read
and the internal data arrays are setup.

             reply	other threads:[~2017-07-31 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 14:58 Dirk-Holger Lenz [this message]
2017-07-31 15:57 ` Dirk-Holger Lenz
2017-07-31 20:23 ` Thomas Monjalon
2017-08-01  8:17   ` Gaëtan Rivet
2017-08-01  9:32     ` Thomas Monjalon
2017-08-02 14: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=9fb283ed-223d-713e-4722-21278f4cfd6e@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).