From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id F14F9377E for ; Wed, 27 Jul 2016 14:58:16 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP; 27 Jul 2016 05:58:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,429,1464678000"; d="scan'208";a="854511935" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga003.jf.intel.com with ESMTP; 27 Jul 2016 05:58:14 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.204]) by IRSMSX153.ger.corp.intel.com ([169.254.9.206]) with mapi id 14.03.0248.002; Wed, 27 Jul 2016 13:58:13 +0100 From: "Mcnamara, John" To: Matthew Hall , Luca Boccassi CC: "dev@dpdk.org" , "christian.ehrhardt@canonical.com" , "cjcollier@linuxfoundation.org" , "ricardo.salveti@linaro.org" Thread-Topic: [dpdk-dev] Compiler hardening flags for libraries and performance implications Thread-Index: AQHR510GcZ/77Nds0kmYApz3O57LTaAsPIOg Date: Wed, 27 Jul 2016 12:58:12 +0000 Message-ID: References: <1469544793.4240.24.camel@brocade.com> <20160726164422.GB1484@mhcomputing.net> In-Reply-To: <20160726164422.GB1484@mhcomputing.net> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMGE3YjE2Y2UtMWQzMC00ZDU2LTk3ZjYtOWMzMzIzM2EyZDIwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InBZQnVvcUFROXJwNFlUMjVyOEUxdDNFYXc2MVBCK1NLajh3bVJBU2FwWnc9In0= x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 12:58:17 -0000 > -----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 > 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 >=20 > 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. >=20 > 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 th= e 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