Calculation of threads in autofp mode is wrong
In runmode autofp the calculation of packet processing threads is wrong IMHO. On a system with 16 cores I end up with 32 threads while detect-thread-ratio is set 1.0 (default) and threads:auto in the af-packet section. So it adds 16 due to the ratio and another 16 from the threads setting in the interface af-packet section. If I change threads: 3 for example I end up with 19 (16+3). If I change thread-ratio to 0.5 while threads: auto I end up with 24 (8 from ratio + 16 from threads auto).
So threads: auto in autofp means amount of cores and this will be added. This doesn't happen in runmode workers for example.
Switching affinity off/on doesn't change anything. Also the threads setting within that section doesn't work either, see #3107.
Updated by Victor Julien almost 4 years ago
Is this an IPS setup or a setup with more than one interface? The number of threads is created per interface.
Updated by Andreas Herz almost 4 years ago
These are all IDS setups and I can even reproduce it with just one interface on my local system.
I tried to look into the code but wasn't sure where the actual calculation happened.
Updated by Andreas Herz over 3 years ago
- Assignee changed from OISF Dev to Andreas Herz
Updated by Victor Julien about 3 years ago
Look and trace things around https://github.com/OISF/suricata/blob/master/src/util-runmodes.c#L108
Updated by Victor Julien almost 3 years ago
- Status changed from Assigned to Closed
- Assignee changed from Andreas Herz to Joshua Lumb
- Target version changed from TBD to 6.0.0beta1