DPDK patches and discussions
 help / color / mirror / Atom feed
From: Cliff Burdick <cburdick@nvidia.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [PATCH] Add support for NVIDIA ARM implementer ID
Date: Fri, 29 Apr 2022 16:50:50 +0000	[thread overview]
Message-ID: <BYAPR12MB3591FA88B312ADDD68E40C76ABFC9@BYAPR12MB3591.namprd12.prod.outlook.com> (raw)

build: added NVIDIA ARM implementer ID

NVIDIA ARM CPUs (Xavier, Grace) use implementer ID 0x4e. This patch adds initial
support for the Xavier chip rather than compiling using the generic platform.

Signed-off-by: Cliff Burdick <cburdick@nvidia.com>
---
 config/arm/meson.build | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/config/arm/meson.build b/config/arm/meson.build
index 8aead74086..91ccbfce2c 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -197,6 +197,23 @@ implementer_hisilicon = {
     }
 }

+implementer_nvidia = {
+    'description': 'NVIDIA',
+    'flags': [
+        ['RTE_MACHINE', '"armv8a"'],
+        ['RTE_USE_C11_MEM_MODEL', true],
+        ['RTE_MAX_LCORE', 256],
+        ['RTE_MAX_NUMA_NODES', 4]
+    ],
+    'part_number_config': {
+        '0x4': {
+            'march': 'armv8-a',
+            'march_features': ['crc'],
+            'compiler_options': ['-moutline-atomics']
+        }
+    }
+}
+
 implementer_qualcomm = {
     'description': 'Qualcomm',
     'flags': [
@@ -224,6 +241,7 @@ implementers = {
     '0x41': implementer_arm,
     '0x43': implementer_cavium,
     '0x48': implementer_hisilicon,
+    '0x4e': implementer_nvidia,
     '0x50': implementer_ampere,
     '0x51': implementer_qualcomm
 }
--
2.17.1

             reply	other threads:[~2022-04-29 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 16:50 Cliff Burdick [this message]
2022-05-09 18:15 Cliff Burdick

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=BYAPR12MB3591FA88B312ADDD68E40C76ABFC9@BYAPR12MB3591.namprd12.prod.outlook.com \
    --to=cburdick@nvidia.com \
    --cc=dev@dpdk.org \
    /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).