From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: luzhipeng <luzhipeng@cestc.cn>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Jan Viktorin <viktorin@rehivetech.com>,
Bruce Richardson <bruce.richardson@intel.com>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: RE: [PATCH] config/arm: add PHYTIUM ft2000plus
Date: Mon, 13 Jun 2022 05:52:35 +0000 [thread overview]
Message-ID: <AS8PR08MB70804FA5BF6BE61C69D731DA9EAB9@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <582505cd-f5f2-77e6-7b00-c439754b0856@cestc.cn>
> -----Original Message-----
> From: luzhipeng <luzhipeng@cestc.cn>
> Sent: Monday, June 13, 2022 11:56 AM
> To: Ruifeng Wang <Ruifeng.Wang@arm.com>; dev@dpdk.org
> Cc: Jan Viktorin <viktorin@rehivetech.com>; Bruce Richardson
> <bruce.richardson@intel.com>; nd <nd@arm.com>
> Subject: Re: [PATCH] config/arm: add PHYTIUM ft2000plus
>
> Thanks
>
> 在 2022/6/13 11:39, Ruifeng Wang 写道:
> >> -----Original Message-----
> >> From: luzhipeng <luzhipeng@cestc.cn>
> >> Sent: Friday, June 10, 2022 1:47 PM
> >> To: dev@dpdk.org
> >> Cc: Jan Viktorin <viktorin@rehivetech.com>; Ruifeng Wang
> >> <Ruifeng.Wang@arm.com>; Bruce Richardson
> >> <bruce.richardson@intel.com>; luzhipeng <luzhipeng@cestc.cn>
> >> Subject: [PATCH] config/arm: add PHYTIUM ft2000plus
> >>
> >> Here adds configs for PHYTIUM server.
> >>
> >> Signed-off-by: luzhipeng <luzhipeng@cestc.cn>
> >
> > I cannot find this patch in Patchwork.
> I send the patch and receive the message:
>
> Your mail to 'dev' with the subject
>
> [PATCH] config/arm: add PHYTIUM ft2000plus
>
> Is being held until the list moderator can review it for approval.
>
> The reason it is being held:
>
> Post by non-member to a members-only list
>
OK. Then you need to register to the dev@dpdk.org mailing list.
https://core.dpdk.org/contribute/#send
>
>
> >
> >> ---
> >> config/arm/arm64_ft2000plus_linux_gcc | 16 ++++++++++++++++
> >> config/arm/meson.build | 26 +++++++++++++++++++++++++-
> >> 2 files changed, 41 insertions(+), 1 deletion(-) create mode
> >> 100644 config/arm/arm64_ft2000plus_linux_gcc
> >>
> >> diff --git a/config/arm/arm64_ft2000plus_linux_gcc
> >> b/config/arm/arm64_ft2000plus_linux_gcc
> >> new file mode 100644
> >> index 0000000000..554517054e
> >> --- /dev/null
> >> +++ b/config/arm/arm64_ft2000plus_linux_gcc
> >> @@ -0,0 +1,16 @@
> >> +[binaries]
> >> +c = 'aarch64-linux-gnu-gcc'
> >
> > You may want to add ccache support when below one is merged.
> > http://patches.dpdk.org/project/dpdk/patch/20220608171304.945454-1-
> jer
> > inj@marvell.com/
> >
> OK,
> >> +cpp = 'aarch64-linux-gnu-cpp'
> >> +ar = 'aarch64-linux-gnu-gcc-ar'
> >> +strip = 'aarch64-linux-gnu-strip'
> >> +pkgconfig = 'aarch64-linux-gnu-pkg-config'
> >> +pcap-config = ''
> >> +
> >> +[host_machine]
> >> +system = 'linux'
> >> +cpu_family = 'aarch64'
> >> +cpu = 'armv8-a'
> >> +endian = 'little'
> >> +
> >> +[properties]
> >> +platform = 'ft2000plus'
> >> diff --git a/config/arm/meson.build b/config/arm/meson.build index
> >> aa12eb76f4..48e5f6af5b 100644
> >> --- a/config/arm/meson.build
> >> +++ b/config/arm/meson.build
> >> @@ -218,6 +218,20 @@ implementer_qualcomm = {
> >> }
> >> }
> >>
> >> +implementer_phytium = {
> >> + 'description': 'PHYTIUM',
> >> + 'flags': [
> >> + ['RTE_MACHINE', '"armv8a"'],
> >> + ['RTE_USE_C11_MEM_MODEL', true],
> >> + ['RTE_CACHE_LINE_SIZE', 64],
> >> + ['RTE_MAX_LCORE', 64],
> >> + ['RTE_MAX_NUMA_NODES', 8]
> >> + ],
> >> + 'part_number_config': {
> >> + '0x662': {'machine_args': ['-march=armv8-a+crc']}
> >> + }
> >> +}
> >> +
> >> ## Arm implementers (ID from MIDR in Arm Architecture Reference
> >> Manual) implementers = {
> >> 'generic': implementer_generic, @@ -225,7 +239,8 @@
> >> implementers = {
> >> '0x43': implementer_cavium,
> >> '0x48': implementer_hisilicon,
> >> '0x50': implementer_ampere,
> >> - '0x51': implementer_qualcomm
> >> + '0x51': implementer_qualcomm,
> >> + '0x70': implementer_phytium
> >> }
> >>
> >> # SoC specific armv8 flags have the highest priority @@ -378,6
> >> +393,13 @@
> >> soc_thunderxt83 = {
> >> 'part_number': '0xa3'
> >> }
> >>
> >> +soc_ft2000plus = {
> >> + 'description': 'PHYTIUM ft2000plus',
> >> + 'implementer': '0x70',
> >> + 'part_number': '0x662',
> >> + 'numa': true
> >> +}
> >> +
> >> '''
> >> Start of SoCs list
> >> generic: Generic un-optimized build for armv8 aarch64 execution
> mode.
> >> @@ -398,6 +420,7 @@ stingray: Broadcom Stingray
> >> thunderx2: Marvell ThunderX2 T99
> >> thunderxt88: Marvell ThunderX T88
> >> thunderxt83: Marvell ThunderX T83
> >> +ft2000plus: PHYTIUM ft2000plus
> >> End of SoCs list
> >> '''
> >> # The string above is included in the documentation, keep it in
> >> sync with the @@ -421,6 +444,7 @@ socs = {
> >> 'thunderx2': soc_thunderx2,
> >> 'thunderxt88': soc_thunderxt88,
> >> 'thunderxt83': soc_thunderxt83,
> >> + 'ft2000plus': soc_ft2000plus,
> >> }
> >>
> >> dpdk_conf.set('RTE_ARCH_ARM', 1)
> >> --
> >> 2.27.0
> >>
> >>
> >
> >
> >
>
next prev parent reply other threads:[~2022-06-13 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 5:46 luzhipeng
2022-06-13 3:39 ` Ruifeng Wang
2022-06-13 3:56 ` luzhipeng
2022-06-13 5:52 ` Ruifeng Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-09 12:21 luzhipeng
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=AS8PR08MB70804FA5BF6BE61C69D731DA9EAB9@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=luzhipeng@cestc.cn \
--cc=nd@arm.com \
--cc=viktorin@rehivetech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).