DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gregory Etelson <getelson@nvidia.com>
To: <dev@dpdk.org>
Cc: getelson@nvidia.com,   <mkashani@nvidia.com>, rasland@nvidia.com
Subject: [PATCH] config/arm: update NVIDIA BlueField-3 configuration
Date: Tue, 18 Feb 2025 12:49:42 +0200	[thread overview]
Message-ID: <20250218104942.81984-1-getelson@nvidia.com> (raw)
In-Reply-To: <20250216140420.216805-1-getelson@nvidia.com>

ARM configuration requires explicit `mcpu` specifications in the
implementor description.

The patch adds `mcpu` and `flags` description for the NVIDIA
BlueField-3 configuration.

Signed-off-by: Gregory Etelson <getelson@nvidia.com>
---
 config/arm/meson.build | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/config/arm/meson.build b/config/arm/meson.build
index 5302861e2c..74f4dd4e1f 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -85,6 +85,11 @@ part_number_config_arm = {
     },
     '0xd42': {
         'march': 'armv8.4-a',
+        'mcpu' : 'cortex-a78ae',
+        'flags': [
+            ['RTE_MAX_LCORE', 16],
+            ['RTE_MAX_NUMA_NODES', 1]
+        ],
     },
     '0xd49': {
         'mcpu': 'neoverse-n2',
-- 
2.45.2


  parent reply	other threads:[~2025-02-18 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-16 14:04 [PATCH] testpmd: support meter_mark init_color in indirect list configuration Gregory Etelson
2025-02-17 16:24 ` Stephen Hemminger
2025-02-17 17:21 ` [PATCH v2] " Gregory Etelson
2025-02-19 18:39   ` Stephen Hemminger
2025-02-20  7:42   ` Ori Kam
2025-02-18 10:49 ` Gregory Etelson [this message]
2025-02-19 16:35   ` [PATCH] config/arm: update NVIDIA BlueField-3 configuration Wathsala Wathawana Vithanage
2025-02-19 17:32     ` 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=20250218104942.81984-1-getelson@nvidia.com \
    --to=getelson@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=mkashani@nvidia.com \
    --cc=rasland@nvidia.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).