From: Thomas Monjalon <thomas@monjalon.net>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK and Link-time Optimizations
Date: Fri, 08 Nov 2019 15:31:44 +0100 [thread overview]
Message-ID: <2903525.fdzLKIPo8T@xps> (raw)
In-Reply-To: <3d280f7e-057f-a35c-bd2f-db401e46e110@ericsson.com>
29/04/2019 18:39, Mattias Rönnblom:
> 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.
That's an interesting point of view.
For info, LTO is merged now.
I would like to see some benchmarks about
LTO static vs shared vs shared without inlines.
Then we could decide what to do with inline functions.
prev parent reply other threads:[~2019-11-08 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 16:39 Mattias Rönnblom
2019-04-29 16:39 ` Mattias Rönnblom
2019-04-29 16:50 ` Stephen Hemminger
2019-04-29 16:50 ` Stephen Hemminger
2019-11-08 14:31 ` Thomas Monjalon [this message]
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=2903525.fdzLKIPo8T@xps \
--to=thomas@monjalon.net \
--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 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).