From owner-freebsd-current@FreeBSD.ORG Mon Jun 1 16:56:46 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 F10EA1065689; Mon, 1 Jun 2009 16:56:46 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id CC02C8FC18; Mon, 1 Jun 2009 16:56:46 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 5D57546B2D; Mon, 1 Jun 2009 12:56:46 -0400 (EDT) Date: Mon, 1 Jun 2009 17:56:46 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Hans Petter Selasky In-Reply-To: <200906011757.31908.hselasky@c2i.net> Message-ID: References: <200906011757.31908.hselasky@c2i.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, 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 16:56:48 -0000 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 Could you provide the trap information and a backtrace? Thanks, Robert N M Watson Computer Laboratory University of Cambridge