From: Thomas Monjalon <thomas@monjalon.net>
To: Dirk-Holger Lenz <dirk.lenz@ng4t.com>, gaetan.rivet@6wind.com
Cc: users@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-users] If shared libraries are used vdev doesn't work anymore
Date: Mon, 31 Jul 2017 22:23:50 +0200 [thread overview]
Message-ID: <2197043.BsW04uu1lT@xps> (raw)
In-Reply-To: <9fb283ed-223d-713e-4722-21278f4cfd6e@ng4t.com>
31/07/2017 16:58, Dirk-Holger Lenz:
> 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.
Yes, you're right: eal_parse_args() is called before eal_plugins_init().
The fix is not small: we should split the args parsing to parse the
device arguments after loading shared libraries.
It is a release blocker.
next parent reply other threads:[~2017-07-31 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9fb283ed-223d-713e-4722-21278f4cfd6e@ng4t.com>
2017-07-31 20:23 ` Thomas Monjalon [this message]
2017-08-01 8:17 ` [dpdk-users] If shared libraries are used vdev doesn't work anymore 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=2197043.BsW04uu1lT@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dirk.lenz@ng4t.com \
--cc=gaetan.rivet@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.