DPDK patches and discussions
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Panu Matilainen <pmatilai@redhat.com>,
	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: Fri, 30 Sep 2016 12:29:49 +0200	[thread overview]
Message-ID: <CAATJJ0+jqRmfCSRm2EGQm0StbSN2M0KiBaY1jgxdVG9R_Zg_yA@mail.gmail.com> (raw)
In-Reply-To: <20160930101522.GB67296@bricha3-MOBL3>

On Fri, Sep 30, 2016 at 12:15 PM, Bruce Richardson <
bruce.richardson@intel.com> wrote:

> To me having some sort of
> naming convention might not be a bad thing, so that we can point it at
> generic
> folders.
>

Distributions don't really agree on the prefix path for the libraries
/usr/lib<changesstarthere>.
So I'd expect that it is hard for someone out there whatever you pick :-/
That said I'd not pick any default by dpdk.org.

In my case I thin I just "left" the linkage discussions too early and by
that forgot to implement RTE_EAL_PMD_PATH which I now did.

If there are no PMDs at all or no matter how many PMDs where there it can't
probe something the error messages might point a bit more towards
the RTE_EAL_PMD_PATH.
E.g. no drivers found, please make sure you have PMDs for your network
devices in <where RTE_EAL_PMD_PATH points to>
And if RTE_EAL_PMD_PATH is "" (=disabled) let them know that as well.
And finally one might suggest trying with EAL option -d.
To then give up and die - just with more words before :-)
That might help.


-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd

  reply	other threads:[~2016-09-30 10:30 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
2016-09-30 10:15     ` Bruce Richardson
2016-09-30 10:29       ` Christian Ehrhardt [this message]
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=CAATJJ0+jqRmfCSRm2EGQm0StbSN2M0KiBaY1jgxdVG9R_Zg_yA@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=bruce.richardson@intel.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).