From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: force gcc to inline rte_movX function Date: Tue, 17 Apr 2018 15:22:06 +0200 Message-ID: <1852475.4XxgDvW1hG@xps> References: <20180412051636.240746-1-junjie.j.chen@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Junjie Chen , bruce.richardson@intel.com, konstantin.ananyev@intel.com Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 619127ED0 for ; Tue, 17 Apr 2018 15:22:09 +0200 (CEST) In-Reply-To: <20180412051636.240746-1-junjie.j.chen@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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?