From: Stephen Hemminger <stephen@networkplumber.org>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK and Link-time Optimizations
Date: Mon, 29 Apr 2019 09:50:42 -0700 [thread overview]
Message-ID: <20190429095042.04b91231@hermes.lan> (raw)
In-Reply-To: <3d280f7e-057f-a35c-bd2f-db401e46e110@ericsson.com>
On Mon, 29 Apr 2019 18:39:47 +0200
Mattias Rönnblom <mattias.ronnblom@ericsson.com> wrote:
> Hi.
>
> Did anyone on the list successfully build DPDK with GCC Link-time
> Optimizations (LTO) enabled? I tried and failed a while back, although
> the detailed reasons of my failure eludes me for the moment.
>
> If LTO builds would work "out of the box", DPDK could gradually migrate
> from away from having static inline functions in the header files.
>
> Those interested squeezing out as much performance as possible would
> build with LTO (and static linking), and those applications who cared
> more about independent upgrades would use dynamic linking and non-LTO
> builds. With the extra cost of using DPDK as a shared library
> (-fPIC-compiled code, more expensive TLS accesses etc), I'm guessing
> this is the case already today.
>
> Regards,
> Mattias
I tried (and it worked) in the past. But you have to be consistent
about always using the same flags. LTO also really makes compiler
a pig and you need multiple Gig of memory.
next prev parent reply other threads:[~2019-04-29 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 16:39 [dpdk-dev] DPDK and Link-time Optimizations Mattias Rönnblom
2019-04-29 16:50 ` Stephen Hemminger [this message]
2019-11-08 14:31 ` Thomas Monjalon
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=20190429095042.04b91231@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mattias.ronnblom@ericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.