Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Aug 2016 12:16:49 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-net@FreeBSD.org
Subject:   [Bug 211836] Kernel panic with net.isr enabled
Message-ID:  <bug-211836-2472-A1Ykywv0Pe@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211836-2472@https.bugs.freebsd.org/bugzilla/>
References:  <bug-211836-2472@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211836

Andrey V. Elsukov <ae@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ae@FreeBSD.org

--- Comment #6 from Andrey V. Elsukov <ae@FreeBSD.org> ---
(In reply to Babak Farrokhi from comment #5)
> (In reply to Andrey V. Elsukov from comment #4)
> So you suggest setting net.isr.maxthreads=3D32 would fix this (aside from
> locking overhead)? Isn't RSS aware of maximum CPUs used by netisr?

I think netisr code should be fixed, we even have in the comment suggested
solution: DPCPU_ID_GET(nws_array[arbitraryvalue % nws_count], nws)

So, probably if we define macro:
#define NETISR_WS(_cpuid)   DPCPU_ID_GET(nws_array[(_cpuid) % nws_count], n=
ws)

Then replace all DPCPU_ID_GET(xxx, nws) with NETISR_WS(xxx), I think this w=
ill
help. But, maybe Robert or Adrian will suggest something better.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211836-2472-A1Ykywv0Pe>