From: Matthew Hall <mhall@mhcomputing.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: Luca Boccassi <lboccass@Brocade.com>,
"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 08:46:37 -0700 [thread overview]
Message-ID: <20160727154637.GB13641@mhcomputing.net> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2025A8562@IRSMSX103.ger.corp.intel.com>
On Wed, Jul 27, 2016 at 12:58:12PM +0000, Mcnamara, John wrote:
> 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
Believe me, I'd really love to do so but I really don't have any clue about
CFLAGS, how to find the problematic LOCs for CPU usage, cache misses, etc. I
think I wrote some previous mails about different challenges I ran into.
I feel like there is a certain amount of knowledge inside of Intel and 6WIND
about these things that hasn't propagated to the rest of the community.
Maybe we could find a way to have some hackathons in Silicon Valley where
people could work on code or projects together? Then we could see about
spreading and documenting some of the organic knowledge to improve the coding
and tuning guides. The Meetups seem to demo new features but they don't talk
about testing and tuning there sadly.
I'm really up for any ideas, it's something I struggled with ever since the
beginning of when I used DPDK 1.x in 2011.
Matthew.
prev parent reply other threads:[~2016-07-27 15:46 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
2016-07-27 15:46 ` Matthew Hall [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=20160727154637.GB13641@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=christian.ehrhardt@canonical.com \
--cc=cjcollier@linuxfoundation.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=lboccass@Brocade.com \
--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).