DPDK patches and discussions
 help / color / mirror / Atom feed
From: Victor Huertas <vhuertas@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Fwd:  Proposal to add a new toolchain for dpdk: g++
Date: Mon, 17 Feb 2020 17:10:13 +0100	[thread overview]
Message-ID: <CAGxG5cjXzXu5t8DifiJJr0u3rCe=0J98n3U7WCNWykVpYgUT3A@mail.gmail.com> (raw)
In-Reply-To: <CAGxG5cjzFb9qJRAAghCrxncdadD4_b4xBxVEYJ=R=x9t0kLfvQ@mail.gmail.com>

Thanks Bruce for your answer,
I will try it and let you know. Although I guess that it makes no
difference if, instead of an exe file, I am compiling a static library
(libmylibrary.a), right?

BTW, I would like to insist on the second issue I was referring to in my
first reply about ip pipeline example using software rings and the latency
detected (which may reach 3-4ms per pipeline transition as long as the two
connected pipelines are configured tu run in the same logical core and the
respective f_run functions are placed in the same thread consecutively).
The thing is that I may have in my application up to 5 o 6 pipelines
interconnected and the accumulated delay detected a ping crossing all these
pipelines becomes 55 ms RTT!!. The latency problem desapeers if I assign a
different logical core to every pipeline.

Thanks a lot for your quick response. It is really appreciated.

Regards,

El lun., 17 feb. 2020 a las 15:40, Bruce Richardson (<
bruce.richardson@intel.com>) escribió:

> On Mon, Feb 17, 2020 at 11:01:21AM +0100, Victor Huertas wrote:
> > Hi all,
> >
> > I am using DPDK development environment to develop an application from
> > which I have to access C++ code.
> > I managed to modify some internal mk files in the dpdk-stable repository
> to
> > allow g++ compiler to be supported.
> >
> > I have all the modified files well identified and I wonder if the support
> > team is interested to add this toolchain in future DPDK releases.
> >
> Rather than trying to build DPDK with g++, or to use the DPDK makefiles
> with your C++ application, can I recommend instead that you treat DPDK as
> any third-party library and build it independently of your application.
>
> If you compile and install DPDK using meson and ninja - or install the
> DPDK package from your linux distro - you will have a 'libdpdk.pc' file
> installed for use by pkg-config. Then for building your application, put in
> the relevant calls to pkg-config i.e. 'pkg-config --cflags libdpdk' and
> 'pkg-config --libs libdpdk', into your app makefile and work from there.
>
> Note too, that all DPDK header files should already be safe for inclusion
> in C++ code - if not, please log a bug.
>
> Regards,
> /Bruce
>


-- 
Victor


-- 
Victor

  parent reply	other threads:[~2020-02-17 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 10:01 [dpdk-dev] " Victor Huertas
2020-02-17 12:33 ` Neil Horman
     [not found]   ` <CAGxG5cj1jf_JQ5df3bYOw7uObBQWb7CdwbJpR9fo8VtcreYwYA@mail.gmail.com>
2020-02-17 16:10     ` [dpdk-dev] Fwd: " Victor Huertas
2020-02-17 14:39 ` [dpdk-dev] " Bruce Richardson
     [not found]   ` <CAGxG5cjzFb9qJRAAghCrxncdadD4_b4xBxVEYJ=R=x9t0kLfvQ@mail.gmail.com>
2020-02-17 16:10     ` Victor Huertas [this message]
2020-02-18 13:12   ` Neil Horman
2020-02-18 14:06     ` Victor Huertas
2020-02-19 11:35       ` Neil Horman

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='CAGxG5cjXzXu5t8DifiJJr0u3rCe=0J98n3U7WCNWykVpYgUT3A@mail.gmail.com' \
    --to=vhuertas@gmail.com \
    --cc=dev@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).