DPDK usage discussions
 help / color / mirror / Atom feed
From: Tomas Jansky <Tomas.Jansky@progress.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Unable to start mlx5 PMD on NUMA node 1
Date: Tue, 25 Jun 2024 10:42:35 +0000	[thread overview]
Message-ID: <SA1PR13MB492543CEAA58C87A607EA484E6D52@SA1PR13MB4925.namprd13.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]

Hello,

I am experiencing issues with DPDK (21.11) mlx5 PMD driver when allocating hugepages on NUMA node 1.

Card info:
  Ethernet controller: Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
  Subsystem: Mellanox Technologies Device 0020
  NUMA node: 1
  Driver: mlx5_core
  Version: 5.7-1.0.2
  Firmware-version: 26.36.1010 (DEL0000000031)

The card is clearly linked to NUMA node 1, so I assigned some hugepages only to the NUMA node 1.
cat /sys/devices/system/node/node0/hugepages/hugepages-1048576kB/nr_hugepages
0
cat /sys/devices/system/node/node1/hugepages/hugepages-1048576kB/nr_hugepages
4

However, when I run my DPDK application, it presents with the following output and fails:
EAL: Detected CPU lcores: 24
EAL: Detected NUMA nodes: 2
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/0000:98:00.0/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No free 1048576 kB hugepages reported on node 0
EAL: No free 2048 kB hugepages reported on node 0
EAL: No free 2048 kB hugepages reported on node 1
EAL: No available 2048 kB hugepages reported
EAL: Probe PCI driver: mlx5_pci (15b3:101f) device: 0000:98:00.0 (socket 1)
mlx5_net: Failed to create ASO bits mem for MR.
EAL: Error: Invalid memory
mlx5_net: probe of PCI device 0000:98:00.0 aborted after encountering an error: Operation not permitted
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:98:00.0 cannot be used
EAL: Bus (pci) probe failed.

If I allocate hugepages only for NUMA node 0, it fails with:
mlx5_common: Failed to initialize global MR share cache.

So the only working solution for me currently is to have hugepages allocated for both NUMA nodes, which is weird, considering that e.g., i40e PMD works completely fine with having hugepages only on a single NUMA node.

Is there a way to force the mlx5 PMD to allocate everything on a single specific NUMA node?

Any advice is appreciated
Tomas


[-- Attachment #2: Type: text/html, Size: 9511 bytes --]

             reply	other threads:[~2024-06-25 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 10:42 Tomas Jansky [this message]
2024-06-25 14:29 ` Erez Ferber

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=SA1PR13MB492543CEAA58C87A607EA484E6D52@SA1PR13MB4925.namprd13.prod.outlook.com \
    --to=tomas.jansky@progress.com \
    --cc=users@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).