DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 887] mlx5: cannot probe ConnectX-6 Dx if socket-limit is too small on NUMA socket 0
Date: Wed, 17 Nov 2021 19:16:25 +0000	[thread overview]
Message-ID: <bug-887-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=887

            Bug ID: 887
           Summary: mlx5: cannot probe ConnectX-6 Dx if socket-limit is
                    too small on NUMA socket 0
           Product: DPDK
           Version: 21.08
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: sunnylandh@gmail.com
  Target Milestone: ---

Our client has a ConnectX-6 Dx Ethernet adapter, installed on a PCI slot
belonging to NUMA socket 1.
When DPDK is initialized with flags "--socket-limit 1,2048 -a c1:00.0", PCI
probe fails with this message:

EAL: No available 2048 kB hugepages reported
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
mlx5_net: probe of PCI device 0000:c1:00.0 aborted after encountering an error:
Cannot allocate memory
mlx5_common: Failed to load driver mlx5_eth
EAL: Requested device 0000:c1:00.0 cannot be used
EAL: Bus (pci) probe failed.

I suspect somewhere in the driver is trying to allocate certain objects on NUMA
socket 0, but I don't know which.
It should be changed to allow allocation on any NUMA socket.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2021-11-17 19:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-887-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).