From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: "terry.montague.1980@btinternet.com"
<terry.montague.1980@btinternet.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Using DPDK with a pre-existing C++ application compiled in Eclipse.
Date: Tue, 20 Jun 2017 16:57:05 +0200 [thread overview]
Message-ID: <20170620145705.GI29091@bidouze.vm.6wind.com> (raw)
In-Reply-To: <12471190.37650.1497970027948.JavaMail.defaultUser@defaultHost>
Hi,
On Tue, Jun 20, 2017 at 03:47:07PM +0100, terry.montague.1980@btinternet.com wrote:
> Hi there,
> Please excuse what to some may appear to be an stupid question.
> I'm trying to use DPDK with an existing C++ application on Linux, using Eclipse Neon.2 as the IDE due to the use of a lot of 3rd party libraries. I'm not using the DPDK build process with the .mk makefiles. I'm just linking to the prebuilt rte_ libs.
> I have got the project to compile, but when running rte_eal_init() with some suitable arguments that I know to be good in a simple standalone application, the PMDs appear to be absent, so the app cannot probe any PCI devices.
> Is there any way this approach is going to work, or do applications that use DPDK have to be compiled as per the example applications with rte.vars.mk/rte.extapp.mk ?
> Thanks in advance.
> Terry
Which NIC are you using? Which PMD do you need?
You can dynamically link specific DPDK drivers using -d in the EAL
parameters. Note that using PMDs as dynamic libraries may slightly
impair performances.
--
Gaëtan Rivet
6WIND
next prev parent reply other threads:[~2017-06-20 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 14:47 terry.montague.1980
2017-06-20 14:57 ` Gaëtan Rivet [this message]
[not found] ` <18287610.38744.1497970879233.JavaMail.defaultUser@defaultHost>
2017-06-20 15:04 ` terry.montague.1980
2017-06-20 15:57 ` Gaëtan Rivet
2017-06-20 16:21 ` terry.montague.1980
2017-06-20 21:15 ` Gaëtan Rivet
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=20170620145705.GI29091@bidouze.vm.6wind.com \
--to=gaetan.rivet@6wind.com \
--cc=terry.montague.1980@btinternet.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).