From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id E0E7A1B46D for ; Wed, 10 Oct 2018 10:48:57 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7BB96205F9; Wed, 10 Oct 2018 04:48:57 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 10 Oct 2018 04:48:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=h9q+r4QqQu56hOw20iEEHvFkl79HDwe/AxpIYumq54o=; b=Da8+Fay/4qeA v7UM11Wu9u0oVXIu9jomYjWZMelyFIySM9+xygAgBhFAE6FrRW1hWMDd28WjGj88 HaS3nLrOumP+06DWweXrneheJLZJ8jew4g/ftNc2jBxT5SamW1XsEz+ElrrmznXw R3zOJBRiLU69ui1Puky1KNXY3a9jBd4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=h9q+r4QqQu56hOw20iEEHvFkl79HDwe/AxpIYumq5 4o=; b=gbFdEIGj1jhfa5EXbtr6RiqYyFrBzSMXjC2fKiOBScuAqTWZoSok4lC6i 5bc8Dw0wNlri2WxU0wlCoW6WhtlGzU+WP528NUseN27FyMtcO8LN+dmjIgPGx74z FpsrIird16Dnvyg2ROKxtKmHMkdcfPDbLMkA2glnyGsU9qv8erOdOlPZYkJgidWW rpqAPOhc4vJTk03aWQQHcRWd40fFY9f6noJOOO6GsLTxz5VvdvCX2+HdFGVKC+Iw uK3qbZ3vHztuXfpIS6+CpX6oG6/TX+iTLg2CZ2JtU1xAp1hFU3K48slR4SgHGElr vnOZdbHvEXedItxNvZ5otKAiEcX9g== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (239.43.136.77.rev.sfr.net [77.136.43.239]) by mail.messagingengine.com (Postfix) with ESMTPA id CE5F9E4532; Wed, 10 Oct 2018 04:48:54 -0400 (EDT) From: Thomas Monjalon To: Honnappa Nagarahalli Cc: "dev@dpdk.org" , "Jacob, Jerin" , "Gavin Hu (Arm Technology China)" , Hemant Agrawal , "debayang. qdt" Date: Wed, 10 Oct 2018 10:48:51 +0200 Message-ID: <4526903.3jovrJyB05@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Correct use of Arm related names X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2018 08:48:58 -0000 10/10/2018 06:37, Honnappa Nagarahalli: > Hi, > This email was triggered by a request to change ARM to Arm in the dpdk.org webpage. I went down the path of finding out the correct names to use. There has not been consistency in using these names across all other projects. So, the recommendation I have got is, 'choose something and use it consistently' (within the DPDK project). Following are my recommendations (please notice the lower/upper case of the letters): > > Architectural State: > aarch64/arm64 - referring to aarch64 state - recommended: aarch64 > aarch32/arm32 - referring to aarch32 state - recommended: aarch32 (arm32 might create confusion with armv7) > > ISA: > armv8.x > armv7.x > > Any reference to Company name: > Arm > > So, everything is lower case except when referring to the company (for ex: Copyright) name. > > Please let me know if you have any questions. There is still confusion about when to use the arch name (aarch64) or the ISA (armv8)? For instance, the lib/librte_eal/common/include/arch/arm/ directory has files split by 32/64 arch. I thought it would make more sense to have different low-level routines depending of the ISA. Is it possible to have armv7 in aarch64? Is it possible to have armv8 in aarch32?