Date: Mon, 1 Jun 2009 17:57:31 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-current@freebsd.org Cc: Robert Watson <rwatson@freebsd.org>, current@freebsd.org Subject: Re: New NETISR implementation, but same defaults Message-ID: <200906011757.31908.hselasky@c2i.net> In-Reply-To: <alpine.BSF.2.00.0906011141530.27214@fledge.watson.org> References: <alpine.BSF.2.00.0906011141530.27214@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906011757.31908.hselasky>