Re: New NETISR implementation, but same defaults

From: Hans Petter Selasky <hselasky_at_c2i.net>
Date: Mon, 1 Jun 2009 17:57:31 +0200
On Monday 01 June 2009, Robert Watson wrote:
> As a HEADS up to 8-CURRENT followers: I've replaced the NETISR
> implementation there as part of on-going work to improve network stack
> parallelism, details below.  In practice, most behavior remains identical
> in the default configuration (direct dispatch, single netisr thread that's
> not bound to a CPU, etc), but people will want to watch out for problems. 
> Some default queue limits have been raised.
>
> More functional changes to take advantage of these features, such as
> deferred ethernet dispatch and software flow ID generation, will follow as
> patches, but probably not ship in 8.0 out of the box.
>

Hi,

Having WITNESS and INVARIANTS in the kernel config I get a panic about a NULL 
mutex when running "dhclient wlan0". Prior to running dhclient wlan0 has been 
properly setup. CPU: 2-HTT

Workaround:

net.isr.direct=0
net.isr.direct_force=0

--HPS
Received on Mon Jun 01 2009 - 13:53:25 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:49 UTC