From owner-freebsd-current@FreeBSD.ORG Mon Jun 1 20:10:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7F23106566B for ; Mon, 1 Jun 2009 20:10:54 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.freebsd.org (Postfix) with ESMTP id 6EE268FC16 for ; Mon, 1 Jun 2009 20:10:53 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=glm44wUnIQYA:10 a=yUlx0E-WNWoA:10 a=kd82vJRRX1Oyphn-8z4A:9 a=1pskUioQH6dtMnrVGHYA:7 a=-fwqlh3ONPwQkAsdr79hbHeIMAEA:4 Received: from [62.113.132.61] (account mc467741@c2i.net HELO [10.37.1.92]) by mailfe04.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 1251419348; Mon, 01 Jun 2009 22:10:52 +0200 From: Hans Petter Selasky To: Robert Watson Date: Mon, 1 Jun 2009 22:15:00 +0200 User-Agent: KMail/1.9.7 References: <200906011757.31908.hselasky@c2i.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906012215.01494.hselasky@c2i.net> Cc: freebsd-current@freebsd.org Subject: Re: New NETISR implementation, but same defaults X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2009 20:10:55 -0000 On Monday 01 June 2009, Robert Watson wrote: > On Mon, 1 Jun 2009, Hans Petter Selasky wrote: > > 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. > > > > 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 > > This should be fixed in r193243. I made a change shortly before merging > that locks the current CPU's workstream before billing packets to it when > direct dispatching, and this turns out to be incorrect, as on systems with > fewer workers than CPUs, then we lock an uninitialized mutex. Let me know > if the above change doesn't fix it. Ok. BTW: I'm booted on a USB harddisk (USB2) and it does not support dump on USB disk yet. I will check if your r193243 does not fix it. Thanks. --HPS