From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jianbo Liu Subject: Re: [PATCH v2 2/3] eal/acl: enable acl for armv7-a Date: Tue, 8 Dec 2015 15:56:16 +0800 Message-ID: References: <1448995276-9599-1-git-send-email-jianbo.liu@linaro.org> <5439330.ZDtZO93Tq2@xps13> <4116700.gN3RbU5N65@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com [209.85.213.46]) by dpdk.org (Postfix) with ESMTP id BF548FFA for ; Tue, 8 Dec 2015 08:56:16 +0100 (CET) Received: by vkha189 with SMTP id a189so7195685vkh.2 for ; Mon, 07 Dec 2015 23:56:16 -0800 (PST) In-Reply-To: <4116700.gN3RbU5N65@xps13> 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" On 8 December 2015 at 10:23, Thomas Monjalon wrote: > 2015-12-08 09:50, Jianbo Liu: >> On 8 December 2015 at 09:18, Thomas Monjalon wrote: >> > 2015-12-03 23:02, Jianbo Liu: >> >> -ifeq ($(CONFIG_RTE_ARCH_ARM64),y) >> >> +ifneq ($(filter y,$(CONFIG_RTE_ARCH_ARM) $(CONFIG_RTE_ARCH_ARM64)),) >> > [...] >> >> +#ifdef RTE_ARCH_ARM >> >> +/* NEON intrinsic vqtbl1q_u8() is not supported in ARMv7-A(AArch32) */ >> > >> > I'm convinced there is a good reason why ARMv8 is also called ARCH_ARM64, >> > and ARMv7 may be called AArch32 or ARCH_ARM. But I don't know why? >> > >> https://lkml.org/lkml/2012/7/15/133 >> >> > Is ARCH_ARM32 or ARCH_ARMv7 too simple? >> > Is it possible to have a 32-bit ARMv8? >> Yes, ARMv8-R/M > > So what does mean CONFIG_RTE_ARCH_ARM? > ARMv7? ARM32? > Please consider a renaming. I'd rather not renaming becase it can be both ARMv7 and AARCH32, which are ISA compatibility. If further differentiation is needed, CONFIG_RTE_ARCH_ARMv7 is added in the config, just like Jan Viktorin did.