Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Mar 2022 17:53:44 +0000
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        "Michael Gmelin" <grembo@freebsd.org>
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:  <3B5E2D6F-5444-4448-B7C3-704E294368C3@lists.zabbadoz.net>
In-Reply-To: <6086BA6D-3D54-4851-B636-3B32FACB35E9@freebsd.org>
References:  <797A280E-5DF2-4276-BB72-E4E1053A19FA@lists.zabbadoz.net> <6086BA6D-3D54-4851-B636-3B32FACB35E9@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Mar 2022, at 17:45, Michael Gmelin wrote:

>> 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?

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B5E2D6F-5444-4448-B7C3-704E294368C3>