From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id 35BAB558A for ; Wed, 27 Jul 2016 17:46:38 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 97461194; Wed, 27 Jul 2016 08:46:37 -0700 (PDT) Date: Wed, 27 Jul 2016 08:46:37 -0700 From: Matthew Hall To: "Mcnamara, John" Cc: Luca Boccassi , "dev@dpdk.org" , "christian.ehrhardt@canonical.com" , "cjcollier@linuxfoundation.org" , "ricardo.salveti@linaro.org" Message-ID: <20160727154637.GB13641@mhcomputing.net> References: <1469544793.4240.24.camel@brocade.com> <20160726164422.GB1484@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [dpdk-dev] Compiler hardening flags for libraries and performance implications X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2016 15:46:38 -0000 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.