From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v5] examples/l3fwd: em path performance fix Date: Fri, 18 Mar 2016 12:00:24 +0100 Message-ID: <1734050.PspUeD4iGQ@xps13> References: <1458293807-2604-1-git-send-email-tomaszx.kulasek@intel.com> <1902439.xcempkFplY@xps13> <20160318105158.GA13693@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, jianbo.liu@linaro.org To: Jerin Jacob , Tomasz Kulasek , Jan Viktorin Return-path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id 77A5C2C00 for ; Fri, 18 Mar 2016 12:01:57 +0100 (CET) Received: by mail-wm0-f48.google.com with SMTP id l68so31621085wml.1 for ; Fri, 18 Mar 2016 04:01:57 -0700 (PDT) In-Reply-To: <20160318105158.GA13693@localhost.localdomain> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-03-18 16:22, Jerin Jacob: > On Fri, Mar 18, 2016 at 11:04:49AM +0100, Thomas Monjalon wrote: > > 2016-03-18 10:52, Tomasz Kulasek: > > > +#if !defined(NO_HASH_MULTI_LOOKUP) && defined(__ARM_NEON) > > > > I think we should use CONFIG_RTE_ARCH_ARM_NEON here. > > Any ARM maintainer to confirm? > > __ARM_NEON should work existing GCC, but it is better to use > RTE_MACHINE_CPUFLAG_NEON as > -it has been generated by probing the compiler capabilities. > -it's future-proof solution to support clang or other gcc versions in > future I agree to use RTE_MACHINE_CPUFLAG_NEON. I just don't understand why CONFIG_RTE_ARCH_ARM_NEON has been introduced. It seems to be used to disable NEON on ARMv7: ifeq ($(CONFIG_RTE_ARCH_ARM_NEON),y) MACHINE_CFLAGS += -mfpu=neon endif