DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Mastorakis, Spyridon" <spyridon.mastorakis@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] "Port 0 is not present on the board" when building DPDK libraries as shared
Date: Fri, 12 May 2017 09:41:25 +0100	[thread overview]
Message-ID: <20170512084124.GA53020@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <84F194B655461746B15919D288BD7AB02877EB@ORSMSX104.amr.corp.intel.com>

On Thu, May 11, 2017 at 09:33:32PM +0000, Mastorakis, Spyridon wrote:
> Hi guys,
> 
> When I compile the DPDK libraries as shared (by modifying the base_config file) and try to run an application (e.g., l3fwd), I get an error that port 0 is not present on board.
> 
> I have cleaned the system several times (unbinded NICs, removed igb_uio and uio modules and hugepage mappings) and have configured everything again, but this does not resolve the issue. I am also not able to add a virtual device (specifically a virtual ring) when I compile as a shared library (no PMD drivers found).
> 
> When I compile the DPDK libraries as static though, everything works perfectly fine and I can run the DPDK applications and add virtual rings.
> 
> I have tried dpdk-17.02 and the latest stable dpdk version (16.11.1), but none of them seems to work.
> 
> Do you have any clue why this is happening?
> 
> Thank you in advance,
> Spyros

When compiled as a shared lib, are you passing in the "-d" parameters to
make sure that the PMDs are actually loaded by the app. Unlike the
static version, they are not automatically linked in the shared lib
build.

/Bruce

  reply	other threads:[~2017-05-12  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 21:33 Mastorakis, Spyridon
2017-05-12  8:41 ` Bruce Richardson [this message]
2017-05-12 15:25   ` Mastorakis, Spyridon

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=20170512084124.GA53020@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=spyridon.mastorakis@intel.com \
    /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).