From: Matthew Hall <mhall@mhcomputing.net>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Difficulty With rte_eal_init()
Date: Fri, 18 Mar 2016 19:45:23 -0700 [thread overview]
Message-ID: <20160319024523.GA24378@mhcomputing.net> (raw)
In-Reply-To: <CA+Gp1naGH4dTm6vkYhu8tXALi9VbHY1xZtrX5EwEzvR3h2g=UQ@mail.gmail.com>
On Fri, Mar 18, 2016 at 04:40:28PM -0700, Cliff Burdick wrote:
> In regards to your fix above, how does this change the probing behavior? It
> seems that it's just combining all the .a files into a single library,
> right?
Without these link flags, the constructor functions, which cause ethdev
drivers to register themselves as probe-able via PCI, do not get invoked
during library load-time, and the probing always screws up, finding zero
working Ethernet ports.
> I still needed to include that whole lost if -D options that the
> examples use, or it still didn't seem to probe the bus. I must be missing
> something else as well.
If you have to pass all these -DRTE_MACHINE_* it is most frequently caused by
an outdated C / C++ compiler. The most recent report of it, which I witnessed,
then saw reported by a second party on the DPDK mailing list, was caused by a
branch of clang which was too old to enable the correct accelerations for
the Haswell, Broadwell, and Skylake series.
The other thing could be you didn't pull in the rte_config.h using -include
$(RTE_INCLUDE)/rte_config.h and -isystem$(RTE_INCLUDE).
Matthew.
next prev parent reply other threads:[~2016-03-19 2:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 21:45 Cliff Burdick
2016-03-18 21:56 ` Matthew Hall
2016-03-18 23:40 ` Cliff Burdick
2016-03-19 2:45 ` Matthew Hall [this message]
2016-03-20 6:16 ` gowrishankar
2016-03-29 21:16 ` Cliff Burdick
2016-03-29 21:30 ` Matthew Hall
2016-03-30 7:49 ` Van Haaren, Harry
2016-03-30 14:16 ` Cliff Burdick
2016-03-30 22:40 ` Matthew Hall
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=20160319024523.GA24378@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=shaklee3@gmail.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).