From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Nathan Speulda <nathan.speulda@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Compiling MLX4 Support into 2.1.0
Date: Fri, 11 Sep 2015 21:09:07 +0200 [thread overview]
Message-ID: <20150911190907.GU4924@6wind.com> (raw)
In-Reply-To: <CANuVPVJ4U5GrW=Cp-y0=HB5ay0Lmo6To=hkQkPSh-BmJMi7+pg@mail.gmail.com>
On Fri, Sep 11, 2015 at 09:51:19AM -0700, Nathan Speulda wrote:
> Thank you for the response,
>
> I followed all of the documentation before I came to the forum on this
> one. OFED is installed and working correctly with all drivers loaded. I
> get to the point of compiling dpdk with support enabled and nothing appears
> to come out during the compile (for mlx4 which is included in the
> .config). My interfaces are not being seen by the PMD though I am aware it
> works differently than the base supported adapters.
I understand you do not see anything like the following lines while DPDK is
being compiled?
== BUILD drivers/net/mlx4
CC mlx4.o
AR librte_pmd_mlx4.a
INSTALL-LIB librte_pmd_mlx4.a
If you don't, something is wrong in your .config, perhaps you haven't
edited the right one? Depending on your target, DPDK may generate another
with default options in an unexpected place and use it instead of your own.
Otherwise, I suggest following Olga's advice, your ports may not be in the
right mode (IB instead of Ethernet), or you're using the wrong kernel
modules in which case mlx4 usually complains during startup.
This is only a guess, please provide compilation, program (testpmd?) startup
logs and the related command line if it still doesn't work.
--
Adrien Mazarguil
6WIND
prev parent reply other threads:[~2015-09-11 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 16:10 Nathan Speulda
2015-09-11 16:35 ` Adrien Mazarguil
2015-09-11 16:51 ` Nathan Speulda
2015-09-11 17:16 ` Olga Shern
2015-09-11 19:09 ` Adrien Mazarguil [this message]
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=20150911190907.GU4924@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nathan.speulda@gmail.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).