From: Stephen Hemminger <stephen@networkplumber.org>
To: "Bill O'Hara" <billtohara@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Moshe Lazer <moshel@mellanox.com>
Subject: Re: [dpdk-dev] Mellanox PMD failure w/DPDK-2.1.0 and MLNX_OFED-3.1-1.0.3
Date: Fri, 16 Oct 2015 13:01:58 -0700 [thread overview]
Message-ID: <20151016130158.02055ce1@xeon-e3> (raw)
In-Reply-To: <CABrJh-eyQPh2N3KSjFCLrA41Sii0ZyzvLRzLZoaVUpFsYsyy2w@mail.gmail.com>
On Fri, 16 Oct 2015 12:11:14 -0700
"Bill O'Hara" <billtohara@gmail.com> wrote:
> Hi Olga,
>
> Sorry for slow response. Initially, raw_ethernet_bw and raw_ethernet_lat
> were not working.
>
> * we clean installed some boxes, rather than upgrading from previous ofed
> etc and now the raw_ethernet_bw and raw_ethernet_lat work. (This is on
> ubuntu14.04 with most recent mellanox ofed release).
>
> * dpdk-2.1 still did not work. We clean installed the build box, to clear
> any possibility of mismatches due to upgrade process. Still not working.
>
> * at the suggestion of one of our developers, we switched from statically
> linking dpdk and libibverbs to static dpdk and dynamic libibverbs. Now the
> dpdk test programs work.
>
> * at this point, we've switched back to our own kernel build (with
> patches), our own dpdk programs, and everything appears to be correct.
>
> Apologies for the firedrill -- we do not yet know the exact root cause, but
> it appears to be related to having done an upgrade of mellanox ofed on the
> ubuntu14.04 boxes AND building with static linking of libibverbs (though we
> double checked that the correct .a file was being linked). I will let you
> know if we have a more satisfactory answer -- we're also more highly
> prioritizing hermetic builds at this point.
>
> thanks for your help and hints!
> bill
Sounds like a case where the application was not linked with proper
LDFLAGS to enable constructors.
next prev parent reply other threads:[~2015-10-16 20:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 3:04 Bill O'Hara
2015-10-08 6:55 ` Olga Shern
2015-10-08 9:03 ` Olga Shern
2015-10-08 16:06 ` Bill O'Hara
2015-10-08 20:55 ` Bill O'Hara
2015-10-08 22:27 ` Olga Shern
2015-10-09 21:17 ` Bill O'Hara
2015-10-15 12:50 ` Olga Shern
2015-10-16 19:11 ` Bill O'Hara
2015-10-16 20:01 ` Stephen Hemminger [this message]
2015-10-17 19:10 ` Olga Shern
2015-10-28 2:32 Dave Engebretsen
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=20151016130158.02055ce1@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=billtohara@gmail.com \
--cc=dev@dpdk.org \
--cc=moshel@mellanox.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).