From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Panu Matilainen <pmatilai@redhat.com>
Cc: Daniele Di Proietto <diproiettod@vmware.com>,
James Page <james.page@canonical.com>, dev <dev@dpdk.org>,
Luca Boccassi <luca.boccassi@gmail.com>
Subject: Re: [dpdk-dev] Did we reduce unnecessary linkage too well?
Date: Thu, 29 Sep 2016 09:26:48 +0200 [thread overview]
Message-ID: <CAATJJ0J3mo-W+1U3zZh9AU=3DBx_1+dZdnz9W5Nmgd5gNoDDxA@mail.gmail.com> (raw)
In-Reply-To: <45bb513b-660d-ba74-44cc-0761c7068df6@redhat.com>
On Thu, Sep 29, 2016 at 9:20 AM, Panu Matilainen <pmatilai@redhat.com>
wrote:
>
> 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.
Great, thanks Panu!
Will create something around that now.
The symlink is about what came to my mind before reading your second
sentence - so good with that.
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2016-09-29 7:27 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
2016-09-29 7:26 ` Christian Ehrhardt [this message]
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='CAATJJ0J3mo-W+1U3zZh9AU=3DBx_1+dZdnz9W5Nmgd5gNoDDxA@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=diproiettod@vmware.com \
--cc=james.page@canonical.com \
--cc=luca.boccassi@gmail.com \
--cc=pmatilai@redhat.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).