Project

General

Profile

Actions
Copy link

Feature #7036

open

Feature #6805: cpu-affinity: enhance CPU affinity logic with per-interface NUMA preferences

DPDK NUMA setup: choose correct CPUs from worker-cpu-set

Added by Adhirath Kabra 7 months ago. Updated 4 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Lukas Sismis
Target version:
8.0.0-beta1
Effort:
Difficulty:
Label:

Description

My machine has even numbered cores on NUMA0 and odd numbered cores on NUMA1. I have defined two vdev interfaces, one on each socket, and defined worker-cpu-set as:
cpu: [ 2,4,6,8,10,12,14,3,5,7,9,11,13,15 ]

The desired behaviour is that first 7 threads (2,4,6,8,10,12,14) use NIC on NUMA0 and the remaining 7 (3,5,7,9,11,13,15) use NIC on NUMA1.

Actual behaviour is that the cpu list is probably sorted internally and read as [ 2,3,4,5,6,7,8,9,10,11,12,13,14,15 ]. As a result, I receive a warning stating -
dpdk: net_bonding0: NIC is on NUMA 0, 3 threads on different NUMA node(s) , which indicates that threads 2-8 are using NIC on NUMA0 and 9-15 are using NIC on NUMA1.

Related issues 3 (3 open — 0 closed)

Related to Suricata - Task #3318: Research: NUMA awarenessNewOISF DevActions
Related to Suricata - Bug #7137: "invalid cpu range" when trying to use CPU affinityNewOISF DevActions
Related to Suricata - Task #7336: Suricon 2024 brainstormNewVictor JulienActions
Actions
Copy link

Also available in: Atom PDF