Is max number of workers in af-xdp mode is limited by rss rx queue number?

Help
1

CPU core 40,
af-xdp setting:

af-xdp:

  • interface: enp132s0f0
    threads: 32

but the hardware only support 16 rss rx queue

> RX flow hash indirection table for enp132s0f0 with 40 RX ring(s):
>     0:      0     1     2     3     4     5     6     7
>     8:      8     9    10    11    12    13    14    15
>    16:      0     1     2     3     4     5     6     7
>    24:      8     9    10    11    12    13    14    15
>    32:      0     1     2     3     4     5     6     7
>    40:      8     9    10    11    12    13    14    15
>    48:      0     1     2     3     4     5     6     7
>    56:      8     9    10    11    12    13    14    15
>    64:      0     1     2     3     4     5     6     7
>    72:      8     9    10    11    12    13    14    15
>    80:      0     1     2     3     4     5     6     7
>    88:      8     9    10    11    12    13    14    15
>    96:      0     1     2     3     4     5     6     7
>   104:      8     9    10    11    12    13    14    15
>   112:      0     1     2     3     4     5     6     7
>   120:      8     9    10    11    12    13    14    15
>

and there is do only 16 workers worked.

Perf: flow-manager: 162 flows processed [FlowRecycler:flow-manager.c:1131]
Perf: flow-manager: 168 flows processed [FlowRecycler:flow-manager.c:1131]
Perf: af-xdp: (W#01-enp132s0f0) Kernel: Packets 36110818, bytes 27525242463, dropped 140138693740633 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#02-enp132s0f0) Kernel: Packets 30831156, bytes 24539517381, dropped 140138592182092 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#03-enp132s0f0) Kernel: Packets 61072808, bytes 26062893962, dropped 140138571179070 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#04-enp132s0f0) Kernel: Packets 55968224, bytes 7906091927, dropped 140136847807029 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#05-enp132s0f0) Kernel: Packets 21967547, bytes 8908673847, dropped 140136822113740 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#06-enp132s0f0) Kernel: Packets 31049232, bytes 18458831638, dropped 140136826799289 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#07-enp132s0f0) Kernel: Packets 33821336, bytes 12092992055, dropped 140135421198109 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#08-enp132s0f0) Kernel: Packets 8450868, bytes 3337256075, dropped 140133508579686 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#09-enp132s0f0) Kernel: Packets 14742481, bytes 7194413696, dropped 140133483407850 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#10-enp132s0f0) Kernel: Packets 16368233, bytes 11447209476, dropped 140133458234989 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#11-enp132s0f0) Kernel: Packets 13661203, bytes 1960638357, dropped 140131881184640 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#12-enp132s0f0) Kernel: Packets 30806444, bytes 13010665408, dropped 140131856028175 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#13-enp132s0f0) Kernel: Packets 40047608, bytes 44050136826, dropped 140131847974232 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#14-enp132s0f0) Kernel: Packets 18879045, bytes 5441547236, dropped 140130522259915 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#15-enp132s0f0) Kernel: Packets 43173756, bytes 19434502812, dropped 140128612238333 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#16-enp132s0f0) Kernel: Packets 24278934, bytes 9771229742, dropped 140128584484030 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#17-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140128559287680 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#18-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140126982237568 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#19-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140126957067648 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#20-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140126948674944 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#21-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140125623283072 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#22-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140123710680448 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#23-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140123685510528 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#24-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140123660340608 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#25-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140122083290496 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#26-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140122058120576 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#27-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140122049727872 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#28-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140120724336000 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#29-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140118811733376 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#30-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140118786563456 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#31-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140118761393536 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Perf: af-xdp: (W#32-enp132s0f0) Kernel: Packets 0, bytes 0, dropped 140117184343424 [ReceiveAFXDPThreadExitStats:source-af-xdp.c:866]
Info: counters: Alerts: 0 [StatsLogSummary:counters.c:871]
Perf: ippair: ippair memory usage: 414144 bytes, maximum: 16777216 [IPPairPrintStats:ippair.c:297]
Info: log-kafka: Kafka poll thread exit success! [kafka_auto_poll:util-log-kafka.c:35]
Perf: host: host memory usage: 398144 bytes, maximum: 536870912 [HostPrintStats:host.c:300]

Here is the cpu info:

image
image1879×218 31.8 KB

Is this in line with expectations? or how can i make use of other cores？

2

What version are you running?
Can you paste the whole suricata.yaml and also how you start Suricata?

You could also check the cpu affinity section in Suricata User Guide — Suricata 7.0.1-dev documentation where you could assing some cores to the management and keep the 16 isolated for the capture workers.