Project

General

Profile

Actions

Bug #6715

closed

dpdk: NUMA warning on non-NUMA system

Added by Victor Julien 4 months ago. Updated about 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Seeing Notice: dpdk: 0000:01:00.0: unable to determine NIC's NUMA node, degraded performance can be expected. This is strange as this is a single CPU / single NUMA system:

$ lscpu
Architecture:            x86_64
...
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-7
...


Subtasks 1 (0 open1 closed)

Bug #6828: dpdk: NUMA warning on non-NUMA system (7.0.x backport)ClosedLukas SismisActions
Actions #1

Updated by Lukas Sismis 2 months ago

  • Status changed from Assigned to In Review
  • Target version changed from TBD to 8.0.0-beta1

Well, yes, this notice is printed out when the DPDK cannot determine the NUMA node through rte_eth_dev_socket_id function.

It is possible to restrain the output to only systems with multiple NUMA nodes.
But I guess it is good to keep in mind that the more performance logs and conditions we add, the more peculiar it might be to maintain it.

I tried to locally retrieve the NUMA node of one of the interface I have locally installed - but it also returns -1

cat /sys/class/net/wlp0s20f3/device/numa_node
-1

The check is now performed only on multi-numa systems:

https://github.com/OISF/suricata/pull/10562

Actions #3

Updated by Lukas Sismis 2 months ago

  • Label Needs backport to 7.0 added
Actions #4

Updated by OISF Ticketbot 2 months ago

  • Subtask #6828 added
Actions #5

Updated by OISF Ticketbot 2 months ago

  • Label deleted (Needs backport to 7.0)
Actions #6

Updated by Lukas Sismis about 2 months ago

  • Status changed from In Review to Resolved
Actions #7

Updated by Lukas Sismis about 2 months ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF