From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH] eal: force gcc to inline rte_movX function Date: Tue, 17 Apr 2018 15:57:34 +0100 Message-ID: <20180417145734.GA89464@bricha3-MOBL.ger.corp.intel.com> References: <20180412051636.240746-1-junjie.j.chen@intel.com> <1852475.4XxgDvW1hG@xps> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Junjie Chen , konstantin.ananyev@intel.com, dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id EAA6AAAB3 for ; Tue, 17 Apr 2018 16:57:39 +0200 (CEST) Content-Disposition: inline In-Reply-To: <1852475.4XxgDvW1hG@xps> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Apr 17, 2018 at 03:22:06PM +0200, Thomas Monjalon wrote: > 12/04/2018 07:16, Junjie Chen: > > From: "Chen, Junjie" > > > > Sometimes gcc does not inline the function despite keyword *inline*, > > we obeserve rte_movX is not inline when doing performance profiling, > > so use *always_inline* keyword to force gcc to inline the function. > > > > Signed-off-by: Chen, Junjie > > --- > > .../common/include/arch/x86/rte_memcpy.h | 22 +++++++++++----------- > > 1 file changed, 11 insertions(+), 11 deletions(-) > > The title should start with "eal/x86:" > Something like that: > eal/x86: force inlining of memcpy sub-functions > > Bruce, Konstantin, any review of the content/optimization? > No objection here. Acked-by: Bruce Richardson