On 13 Mar 2022, at 17:45, Michael Gmelin wrote:
On 13. Mar 2022, at 18:16, Bjoern A. Zeeb
<bzeeb-li...@lists.zabbadoz.net> wrote:
On 13 Mar 2022, at 16:33, Michael Gmelin wrote:
It's important to point out that this only happens with kern.ncpu>1.
With kern.ncpu==1 nothing gets stuck.
This perfectly fits into the picture, since, as pointed out by
Johan,
the first commit that is affected[0] is about multicore support.
Ignore my ignorance, what is the default of net.isr.maxthreads and
net.isr.bindthreads (in stable/13) these days?
My tests were on CURRENT and I’m afk, but according to cgit[0][1],
max is 1 and bind is 0.
Would it make sense to repeat the test with max=-1?
I’d say yes, I’d also bind, but that’s just me.
I would almost assume Kristof running with -1 by default (but he can
chime in on that).
Best
Michael
[0] https://cgit.freebsd.org/src/tree/sys/net/netisr.c#n280
[1]
https://cgit.freebsd.org/src/tree/sys/net/netisr.c?h=stable%2F13#n280
