From: Yutang Jiang <jiangyutang@os.amperecomputing.com>
To: dev@dpdk.org
Cc: patches@amperecomputing.com, yutang.jiang@amperecomputing.com,
jiangyutang@os.amperecomputing.com, ruifeng.wang@arm.com,
nd@arm.com, juraj.linkes@pantheon.tech,
wathsala.vithanage@arm.com, thomas@monjalon.net,
honnappa.nagarahalli@arm.com
Subject: [DPDK][PATCH v4] config/arm: add Ampere AmpereOneAC04 platform
Date: Thu, 27 Jun 2024 23:22:47 -0400 [thread overview]
Message-ID: <20240628032247.10414-1-jiangyutang@os.amperecomputing.com> (raw)
The AmpereOneAC04 is efficient Cloud Native CPU:
Up to 192 Cores
2MB Private L2 Cache per Core
8 channel DDR5
128 lanes PCIe Gen5
Signed-off-by: Yutang Jiang <jiangyutang@os.amperecomputing.com>
---
config/arm/arm64_ampereoneac04_linux_gcc | 17 +++++++++++++++++
config/arm/meson.build | 19 +++++++++++++++++++
2 files changed, 36 insertions(+)
create mode 100644 config/arm/arm64_ampereoneac04_linux_gcc
diff --git a/config/arm/arm64_ampereoneac04_linux_gcc b/config/arm/arm64_ampereoneac04_linux_gcc
new file mode 100644
index 0000000000..a8dfd6551f
--- /dev/null
+++ b/config/arm/arm64_ampereoneac04_linux_gcc
@@ -0,0 +1,17 @@
+[binaries]
+c = ['ccache', 'aarch64-linux-gnu-gcc']
+cpp = ['ccache', 'aarch64-linux-gnu-g++']
+ar = 'aarch64-linux-gnu-gcc-ar'
+strip = 'aarch64-linux-gnu-strip'
+pkgconfig = 'aarch64-linux-gnu-pkg-config'
+pkg-config = 'aarch64-linux-gnu-pkg-config'
+pcap-config = ''
+
+[host_machine]
+system = 'linux'
+cpu_family = 'aarch64'
+cpu = 'armv8.6-a'
+endian = 'little'
+
+[properties]
+platform = 'ampereoneac04'
diff --git a/config/arm/meson.build b/config/arm/meson.build
index a45aa9e466..012935d5d7 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -210,6 +210,16 @@ implementer_ampere = {
['RTE_MAX_LCORE', 320],
['RTE_MAX_NUMA_NODES', 8]
]
+ },
+ '0xac4': {
+ 'march': 'armv8.6-a',
+ 'march_features': ['crc', 'crypto'],
+ 'mcpu': 'ampere1a',
+ 'flags': [
+ ['RTE_MACHINE', '"AmpereOneAC04"'],
+ ['RTE_MAX_LCORE', 384],
+ ['RTE_MAX_NUMA_NODES', 8]
+ ]
}
}
}
@@ -371,6 +381,13 @@ soc_ampereone = {
'numa': true
}
+soc_ampereoneac04 = {
+ 'description': 'Ampere AmpereOne AC04',
+ 'implementer': '0xc0',
+ 'part_number': '0xac4',
+ 'numa': true
+}
+
soc_armada = {
'description': 'Marvell ARMADA',
'implementer': '0x41',
@@ -621,6 +638,7 @@ generic: Generic un-optimized build for armv8 aarch64 execution mode.
generic_aarch32: Generic un-optimized build for armv8 aarch32 execution mode.
altra: Ampere Altra/AltraMax
ampereone: Ampere AmpereOne
+ampereoneac04: Ampere AmpereOneAC04
armada: Marvell ARMADA
bluefield: NVIDIA BlueField
bluefield3: NVIDIA BlueField-3
@@ -658,6 +676,7 @@ socs = {
'generic_aarch32': soc_generic_aarch32,
'altra': soc_altra,
'ampereone': soc_ampereone,
+ 'ampereoneac04': soc_ampereoneac04,
'armada': soc_armada,
'bluefield': soc_bluefield,
'bluefield3': soc_bluefield3,
--
2.43.0
next reply other threads:[~2024-06-28 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 3:22 Yutang Jiang [this message]
2024-06-28 3:30 ` Yutang Jiang
2024-07-01 9:27 ` Ruifeng Wang
2024-07-07 13:46 ` Thomas Monjalon
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=20240628032247.10414-1-jiangyutang@os.amperecomputing.com \
--to=jiangyutang@os.amperecomputing.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=patches@amperecomputing.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=wathsala.vithanage@arm.com \
--cc=yutang.jiang@amperecomputing.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).