From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] arm: detect NEON by RTE_MACHINE_CPUFLAG_NEON flag only Date: Fri, 18 Mar 2016 14:49:57 +0100 Message-ID: <18259292.OJteoyVp0E@xps13> References: <20160318130019.4715e5d5@pcviktorin.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Jerin Jacob , Tomasz Kulasek , dev@dpdk.org, jianbo.liu@linaro.org To: viktorin@rehivetech.com Return-path: Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 35C175586 for ; Fri, 18 Mar 2016 14:51:29 +0100 (CET) Received: by mail-wm0-f46.google.com with SMTP id l124so31978427wmf.1 for ; Fri, 18 Mar 2016 06:51:29 -0700 (PDT) In-Reply-To: <20160318130019.4715e5d5@pcviktorin.fit.vutbr.cz> 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 13:00, Jan Viktorin: > The RTE_MACHINE_CPUFLAG_NEON was only a result of the gcc testing. > However, the target CPU may not support NEON or the user can disable to > use it (as it does not always improve the performance). > > The RTE_MACHINE_CPUFLAG_NEON detection is now based on both, the > __ARM_NEON_FP feature from gcc and CONFIG_RTE_ARCH_ARM_NEON from > the .config. The memcpy implemention is driven by > RTE_MACHINE_CPUFLAG_NEON, so the reason to disable neon is hidden for > the actual code. > > Signed-off-by: Jan Viktorin > --- > > I can also include this one: > > examples/l3fwd/l3fwd_em.c:253:#elif defined(__ARM_NEON) Yes please. I will set my patch as superseded.