From: Thomas Monjalon <thomas@monjalon.net>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Sachin Saxena <sachin.saxena@nxp.com>,
Wei Zhao <wei.zhao1@intel.com>, Jeff Guo <jia.guo@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Zhihong Wang <zhihong.wang@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Jan Viktorin <viktorin@rehivetech.com>,
dev@dpdk.org, jerinj@marvell.com, honnappa.nagarahalli@arm.com,
phil.yang@arm.com, nd@arm.com
Subject: Re: [dpdk-dev] [PATCH v1] config: remap flags used for Arm platforms
Date: Tue, 13 Oct 2020 16:26:20 +0200 [thread overview]
Message-ID: <14978748.slpD515BXZ@thomas> (raw)
In-Reply-To: <20200911153959.204042-1-ruifeng.wang@arm.com>
11/09/2020 17:39, Ruifeng Wang:
> RTE_ARCH_xx flags are used to distinguish platform architectures.
> These flags can be used to pick different code paths for different
> architectures at compile time.
> For Arm platforms, there are 3 flags in use: RTE_ARCH_ARM,
> RTE_ARCH_ARMv7 and RTE_ARCH_ARM64.
> RTE_ARCH_ARM64 is for 64-bit aarch64 platforms,
> and RTE_ARCH_ARM & RTE_ARCH_ARMv7 are for 32-bit platforms.
> RTE_ARCH_ARMv7 is for ARMv7 platforms as its name suggested.
>
> The issue is meaning of RTE_ARCH_ARM is not clear enough.
> Because no info about platform word length is included in the name.
> To make the flag names more clear, a naming scheme is proposed.
>
> RTE_ARCH_ARM (all Arm platforms)
> |
> +----RTE_ARCH_32 (New. 32-bit platforms of all architectures)
> | |
> | +----RTE_ARCH_ARMv7 (ARMv7 platforms)
> | |
> | +----RTE_ARCH_ARMv8_AARCH32 (aarch32 state on aarch64 machine)
> |
> +----RTE_ARCH_64 (64-bit platforms of all architectures)
> |
> +----RTE_ARCH_ARM64 (64-bit Arm platforms)
>
> RTE_ARCH_32 will be explicitly defined for 32-bit platforms.
>
> To fit into the new naming scheme, current usage of RTE_ARCH_ARM in
> project is mapped to (RTE_ARCH_ARM && RTE_ARCH_32).
>
> Matching flags for other architectures are:
> RTE_ARCH_X86
> |
> +----RTE_ARCH_32
> | |
> | +----RTE_ARCH_I686
> | |
> | +----RTE_ARCH_X86_X32
> |
> +----RTE_ARCH_64
> |
> +----RTE_ARCH_X86_64
>
> RTE_ARCH_PPC_64 ---- RTE_ARCH_64
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Phil Yang <phil.yang@arm.com>
Applied, thanks
prev parent reply other threads:[~2020-10-13 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 15:39 [dpdk-dev] [PATCH v1] config: remap flags used for Arm platforms Ruifeng Wang
2020-09-29 13:38 ` Ruifeng Wang
2020-10-13 14:26 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14978748.slpD515BXZ@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=jia.guo@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nd@arm.com \
--cc=phil.yang@arm.com \
--cc=ruifeng.wang@arm.com \
--cc=sachin.saxena@nxp.com \
--cc=viktorin@rehivetech.com \
--cc=vladimir.medvedkin@intel.com \
--cc=wei.zhao1@intel.com \
--cc=zhihong.wang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.