DPDK patches and discussions
 help / color / mirror / Atom feed
* [Bug 887] mlx5: cannot probe ConnectX-6 Dx if socket-limit is too small on NUMA socket 0
@ 2021-11-17 19:16 bugzilla
  0 siblings, 0 replies; only message in thread
From: bugzilla @ 2021-11-17 19:16 UTC (permalink / raw)
  To: dev

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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-11-17 19:16 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-17 19:16 [Bug 887] mlx5: cannot probe ConnectX-6 Dx if socket-limit is too small on NUMA socket 0 bugzilla

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).