Date: Sun, 13 Mar 2022 18:45:44 +0100 From: Michael Gmelin <grembo@freebsd.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: Johan Hendriks <joh.hendriks@gmail.com>, Kristof Provost <kp@freebsd.org>, "Patrick M. Hausen" <hausen@punkt.de>, freeBSD-net <freebsd-net@freebsd.org> Subject: Re: epair and vnet jail loose connection. Message-ID: <6086BA6D-3D54-4851-B636-3B32FACB35E9@freebsd.org> In-Reply-To: <797A280E-5DF2-4276-BB72-E4E1053A19FA@lists.zabbadoz.net>
index | next in thread | previous in thread | raw e-mail
> On 13. Mar 2022, at 18:16, Bjoern A. Zeeb <bzeeb-lists@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? 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#n280home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6086BA6D-3D54-4851-B636-3B32FACB35E9>