From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK and Link-time Optimizations
Date: Mon, 29 Apr 2019 18:39:47 +0200 [thread overview]
Message-ID: <3d280f7e-057f-a35c-bd2f-db401e46e110@ericsson.com> (raw)
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
next reply other threads:[~2019-04-29 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 16:39 Mattias Rönnblom [this message]
2019-04-29 16:50 ` [dpdk-dev] DPDK and Link-time Optimizations Stephen Hemminger
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=3d280f7e-057f-a35c-bd2f-db401e46e110@ericsson.com \
--to=mattias.ronnblom@ericsson.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).