From: Panu Matilainen <pmatilai@redhat.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Daniele Di Proietto <diproiettod@vmware.com>,
James Page <james.page@canonical.com>, dev <dev@dpdk.org>
Cc: Luca Boccassi <luca.boccassi@gmail.com>
Subject: Re: [dpdk-dev] Did we reduce unnecessary linkage too well?
Date: Thu, 29 Sep 2016 10:20:20 +0300 [thread overview]
Message-ID: <45bb513b-660d-ba74-44cc-0761c7068df6@redhat.com> (raw)
In-Reply-To: <CAATJJ0LY_h8+A=7An7xysVSjeOfM4MWdDLEtNrYoW2Qnap04cQ@mail.gmail.com>
On 09/29/2016 09:58 AM, Christian Ehrhardt wrote:
> Hi,
> I was finally getting to more deeply re-validate Openvswitch 2.6 together
> with DPDK 16.07. And I think I found a whiplash of our effort to reduce
> unnecessary hard linkage.
>
> Trying to avoid cross-posting, picking DPDK list and the main involved
> people on TO/CC.
>
> TL;DR:
> - pmd drivers are no more "auto"-loaded
> - adding -d ...so to all consuming applications feels obnoxious
> - do we really have to intentionally overlink some?
> - I hope I just overlook something trivial to fix this.
Yup. Set CONFIG_RTE_EAL_PMD_PATH to the path where your PMDs are
installed. Note that since the plugin autoloader in DPDK doesn't make
assumptions about names, it'll try to load *everything* in that path, so
you don't want it pointing to eg /usr/lib directly.
What we have on Fedora and RHEL is a /usr/lib(64)/dpdk-pmds/ directory
with symlinks to the actual pmds which reside in /usr/lib(64) because
some of them provide actual API.
- Panu -
next prev parent reply other threads:[~2016-09-29 7:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 6:58 Christian Ehrhardt
2016-09-29 7:20 ` Panu Matilainen [this message]
2016-09-29 7:26 ` Christian Ehrhardt
2016-09-30 10:15 ` Bruce Richardson
2016-09-30 10:29 ` Christian Ehrhardt
2016-09-30 10:31 ` Panu Matilainen
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=45bb513b-660d-ba74-44cc-0761c7068df6@redhat.com \
--to=pmatilai@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=diproiettod@vmware.com \
--cc=james.page@canonical.com \
--cc=luca.boccassi@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).