dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 333] PCI devices not found when DPDK is linked as dynamic libraries
Date: Fri, 19 Jul 2019 20:43:04 +0000	[thread overview]
Message-ID: <bug-333-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=333

            Bug ID: 333
           Summary: PCI devices not found when DPDK is linked as dynamic
                    libraries
           Product: DPDK
           Version: 19.08
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

If DPDK is configured with RTE_SHARED_LIB=y then applications are not loading
the required PCI library and therefore devices are not found.

Example is that l3fwd works if linked statically but fails if built with shared
libraries.

# ./examples/l3fwd/build/l3fwd -n4 -l0-3 -w 02:00.0
EAL: Detected 8 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: failed to parse device "02:00.0"
EAL: Unable to parse device '02:00.0'
EAL: Error - exiting with code: 1
   Cause: Invalid EAL parameters  

The string 02:00.0 should have been parsed by PCI library and that will find
the device. but since library is not pulled in, the device is not found.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-07-19 20:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 20:43 bugzilla [this message]
2019-07-19 23:17 ` [dpdk-dev] [Bug 333] PCI devices not found when DPDK is linked as dynamic libraries Stephen Hemminger

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=bug-333-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).