From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Matthew Hall <mhall@mhcomputing.net>,
Luca Boccassi <lboccass@Brocade.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>,
"cjcollier@linuxfoundation.org" <cjcollier@linuxfoundation.org>,
"ricardo.salveti@linaro.org" <ricardo.salveti@linaro.org>
Subject: Re: [dpdk-dev] Compiler hardening flags for libraries and performance implications
Date: Wed, 27 Jul 2016 12:58:12 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2025A8562@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20160726164422.GB1484@mhcomputing.net>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Matthew Hall
> Sent: Tuesday, July 26, 2016 5:44 PM
> To: Luca Boccassi <lboccass@Brocade.com>
> Cc: dev@dpdk.org; christian.ehrhardt@canonical.com;
> cjcollier@linuxfoundation.org; ricardo.salveti@linaro.org
> Subject: Re: [dpdk-dev] Compiler hardening flags for libraries and
> performance implications
>
> On Tue, Jul 26, 2016 at 02:53:13PM +0000, Luca Boccassi wrote:
> > While working on uploading DPDK to Ubuntu and Debian, we were
> > wondering if anyone had any thoughts/opinions on enabling compiler
> > hardening flags for the DPDK libraries and the possible performance
> implications.
>
> Most of the C profilers, both VTune and Perf based tools, have not given
> me that much helpful data. They make it very hard to go from slow
> functions down to actual slow lines of code causing performance issues
> that I should fix. So I would love to see a MUCH better DPDK tuning guide,
> because the current one is really generic and gives no useful advice
> beyond what any programmer has already heard many times that doesn't
> really add much value.
Hi Matthew,
Maybe you kick this off and submit something to the new howto section of the docs with whatever tuning tips you have so far.
Then we can get people to contribute over time until we have something more useful.
John
next prev parent reply other threads:[~2016-07-27 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 14:53 Luca Boccassi
2016-07-26 16:44 ` Matthew Hall
2016-07-27 12:58 ` Mcnamara, John [this message]
2016-07-27 15:46 ` Matthew Hall
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=B27915DBBA3421428155699D51E4CFE2025A8562@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=cjcollier@linuxfoundation.org \
--cc=dev@dpdk.org \
--cc=lboccass@Brocade.com \
--cc=mhall@mhcomputing.net \
--cc=ricardo.salveti@linaro.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).