From: Cliff Burdick <shaklee3@gmail.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Difficulty With rte_eal_init()
Date: Fri, 18 Mar 2016 16:40:28 -0700 [thread overview]
Message-ID: <CA+Gp1naGH4dTm6vkYhu8tXALi9VbHY1xZtrX5EwEzvR3h2g=UQ@mail.gmail.com> (raw)
In-Reply-To: <20160318215602.GC23135@mhcomputing.net>
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? 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. Do you mind pasting all of the defines/libraries
that you pass into your app to get it to work? Currently the examples in
mine pass this large list:
-march=native -DRTE_MACHINE_CPUFLAG_SSE -DRTE_MACHINE_CPUFLAG_SSE2
-DRTE_MACHINE_CPUFLAG_SSE3 -DRTE_MACHINE_CPUFLAG_SSSE3
-DRTE_MACHINE_CPUFLAG_SSE4_1 -DRTE_MACHINE_CPUFLAG_SSE4_2
-DRTE_MACHINE_CPUFLAG_PCLMULQDQ -DRTE_MACHINE_CPUFLAG_AVX
-DRTE_MACHINE_CPUFLAG_RDRAND -DRTE_MACHINE_CPUFLAG_FSGSBASE
-DRTE_MACHINE_CPUFLAG_F16C -DRTE_MACHINE_CPUFLAG_AVX2
-DRTE_COMPILE_TIME_CPUFLAGS=RTE_CPUFLAG_SSE,RTE_CPUFLAG_SSE2,RTE_CPUFLAG_SSE3,RTE_CPUFLAG_SSSE3,RTE_CPUFLAG_SSE4_1,RTE_CPUFLAG_SSE4_2,RTE_CPUFLAG_PCLMULQDQ,RTE_CPUFLAG_AVX,RTE_CPUFLAG_RDRAND,RTE_CPUFLAG_FSGSBASE,RTE_CPUFLAG_F16C,RTE_CPUFLAG_AVX2
-include $(RTE_SDK)/include/rte_config.h -O3
On Fri, Mar 18, 2016 at 2:56 PM, Matthew Hall <mhall@mhcomputing.net> wrote:
> On Fri, Mar 18, 2016 at 02:45:10PM -0700, Cliff Burdick wrote:
> > Hi, I've been trying to create a standalone application linked against
> > DPDK, and I'm having some issues getting the program to run properly. The
> > main problem is that in my standalone app compared to the example code,
> > rte_eal_init() from the example code seems to probe the PCI bus, whereas
> > mine doesn't.
> [SNIP]
> > However, when I then tried compiling the dpdk part of my app into a
> library
> > and linking against it from my main program, the PCI scanning goes away
> and
> > no devices are found.
>
> This hoses up every new app developer. Especially me, as I used DPDK before
> the PCI probe behavior was changed between versions and got totally lost
> when
> it broke. You need the following:
>
> Build Configuration:
>
> CONFIG_RTE_BUILD_COMBINE_LIBS=y
>
> Linker Flags (LDFLAGS):
>
> -Wl,--whole-archive -Wl,--start-group -ldpdk -Wl,--end-group
> -Wl,--no-whole-archive
>
> Sincerely.
> Matthew.
>
next prev parent reply other threads:[~2016-03-18 23:40 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 [this message]
2016-03-19 2:45 ` Matthew Hall
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='CA+Gp1naGH4dTm6vkYhu8tXALi9VbHY1xZtrX5EwEzvR3h2g=UQ@mail.gmail.com' \
--to=shaklee3@gmail.com \
--cc=mhall@mhcomputing.net \
--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).