You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the case of cluster_qm and fixed affinity settings between network queues and cpu cores it is necessary that the suricata affinity settings and suricata interface settings are aligned.
Example:
enp94s0f0 cluster_qm mode with cpu cores 1-9 assigned on NUMA node 0 via set_irq_affinity and RSS Queues
enp94s0f1 cluster_qm mode with cpu cores 21-29 assigned o NUMA node 0 via set_irq_affinity and RSS Queues
enp175s0f0 cluster_flow mode with cpu cores 11-19 assigned on NUMA node 1
This requires that the worker-cpu-set is set to [ ""1-9","21-29", "11-19" ] if the interface config has the order enp94s0f0, enp94s0f1, enp175s0f0 as suricata picks the cores in order of the interface config.
So if [ ""1-9","11-19", "21-29" ] would be set enp94s0f1 would use the cores 11-19 although it should use 21-29.
This could change in the future if Suricata changes the behaviour or the interface settings can define the cores directly.
The text was updated successfully, but these errors were encountered:
In the case of cluster_qm and fixed affinity settings between network queues and cpu cores it is necessary that the suricata affinity settings and suricata interface settings are aligned.
Example:
This requires that the worker-cpu-set is set to [ ""1-9","21-29", "11-19" ] if the interface config has the order enp94s0f0, enp94s0f1, enp175s0f0 as suricata picks the cores in order of the interface config.
So if [ ""1-9","11-19", "21-29" ] would be set enp94s0f1 would use the cores 11-19 although it should use 21-29.
This could change in the future if Suricata changes the behaviour or the interface settings can define the cores directly.
The text was updated successfully, but these errors were encountered: