public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Bing Zhao <bingz@nvidia.com>
To: <dev@dpdk.org>
Cc: <wathsala.vithanage@arm.com>, <bruce.richardson@intel.com>,
	<honnappa.nagarahalli@arm.com>, <ruifeng.wang@arm.com>,
	<thomas@monjalon.net>, <stable@dpdk.org>
Subject: [PATCH] config/arm: fix the cacheline size for Grace CPU
Date: Tue, 17 Mar 2026 11:17:32 +0200	[thread overview]
Message-ID: <20260317091732.289777-1-bingz@nvidia.com> (raw)

The Nvidia Grace platform has a cacheline size with 64B, unlike the
128B size on other arm64 generic platforms. In the meson file, the
cacheline size is missing to be defined explicitly. So it will choose
128 for building and it will impact the performance.

In the ACM whitepaper, "The NVIDIA Grace CPU implements 72 Neoverse V2
Cores [16] with a 64-B cache line size".

Reference link:
https://dl.acm.org/doi/10.1145/3723851.3723853

Fixes: d007038c0121 ("config/arm: add NVIDIA Grace CPU")
Cc: honnappa.nagarahalli@arm.com
Cc: stable@dpdk.org

Signed-off-by: Bing Zhao <bingz@nvidia.com>
---
 config/arm/meson.build | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/config/arm/meson.build b/config/arm/meson.build
index 523b0fc0ed..f7eac7da0a 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -535,6 +535,9 @@ soc_grace = {
     'implementer': '0x41',
     'part_number': '0xd4f',
     'extra_march_features': ['crypto'],
+    'flags': [
+        ['RTE_CACHE_LINE_SIZE', '"64"'],
+    ],
     'numa': true
 }
 
-- 
2.34.1


             reply	other threads:[~2026-03-17  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17  9:17 Bing Zhao [this message]
2026-03-17  9:55 ` [PATCH] config/arm: fix the cacheline size for Grace CPU 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=20260317091732.289777-1-bingz@nvidia.com \
    --to=bingz@nvidia.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=wathsala.vithanage@arm.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