From: "Wiles, Keith" <keith.wiles@intel.com>
To: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Network Devices
Date: Sun, 18 Dec 2016 15:35:29 +0000 [thread overview]
Message-ID: <A561F879-A165-4252-A812-EA0DC4EC8514@intel.com> (raw)
In-Reply-To: <1394E9B2-BED1-49DA-A14E-EB5257E26F9E@cloudsimple.com>
> On Dec 18, 2016, at 12:01 AM, Kumaraparameshwaran Rathnavel <krath@cloudsimple.com> wrote:
>
> Hi All,
>
> I am writing my own application and in Makefile I just use include files and library path of the DPDK. It is not able to find any pci devices during rte_eal_pci_init. I am not getting any Network devices but when I use DPDKs example Makefile I am able get the devices. What should be the reason for this as in both cases the function is the same.
The makefiles in the DPDK examples include DPDK make fragment files *.mk, these files include the mk/rte.app.mk fragment and it appends the libraries on to the end of the link line including the drivers. The drivers do not use a strong compiler link to be included in the image. What happens is the rte.app.mk will include the drivers and the use constructor calls to bind to DPDK.
I hope that is clearer. One way to add a driver is to include its .o on the link line of your makefile or try using the examples directory style of Makefile in your application.
>
> Thanking you,
> Param.
>
Regards,
Keith
next prev parent reply other threads:[~2016-12-18 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 6:01 Kumaraparameshwaran Rathnavel
2016-12-18 15:35 ` Wiles, Keith [this message]
2016-12-18 16:19 ` Kumaraparameshwaran Rathnavel
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=A561F879-A165-4252-A812-EA0DC4EC8514@intel.com \
--to=keith.wiles@intel.com \
--cc=krath@cloudsimple.com \
--cc=users@dpdk.org \
/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).