From owner-freebsd-current@FreeBSD.ORG Fri Jun 1 12:23:27 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 86A8616A473; Fri, 1 Jun 2007 12:23:27 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.swip.net [212.247.154.65]) by mx1.freebsd.org (Postfix) with ESMTP id 9FA2313C45A; Fri, 1 Jun 2007 12:23:26 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.lan) by mailfe03.swip.net (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 515030283; Fri, 01 Jun 2007 14:23:22 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 1 Jun 2007 14:23:13 +0200 User-Agent: KMail/1.9.5 References: <20070601105521.D77697@fledge.watson.org> In-Reply-To: <20070601105521.D77697@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706011423.13320.hselasky@c2i.net> Cc: Robert Watson , current@freebsd.org Subject: Re: NET_NEEDS_GIANT removal 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: Fri, 01 Jun 2007 12:23:27 -0000 On Friday 01 June 2007 12:13, Robert Watson wrote: > Dear all, > > Another of the things in flight for 7.0 is the removal of NET_NEEDS_GIANT. > This is the compatibility code that allows non-MPSAFE network protocols to > operate--when they are compiled into the kernel, Giant is forced over the > entire network stack. This allows them to run moderately safely, but > eliminates use of more than one processor at a time in any part of the > network stack, as well as increasing contention on Giant for any other > non-MPSAFE components, requiring Giant be acquired in possible shared > ithreads, etc. The components currently requiring Giant are: > > i4b - ISDN implementation > netatm - One of three ATM implementations > ng_h4 - tty line discipline for bluetooth serial (?) > KAME IPSEC - One of two IPSEC implementations > IPX over IP - IPX over IP tunnel support > > Of these, I have patches for IPX over IP (but no testers despite several > e-mails to mailing lists), and George has patches that add IPv6 support to > FAST_IPSEC and remove KAME IPSEC, currently in testing on the net@ mailing > list. Skip Ford has been working on locking for netatm, but I'm not sure > what the current status is. Bjoern has been starting to look at i4b but > has let me know that it is unlikely this will be done before 7.1. I have > no information on the status of ng_h4, but it may well be that its > involvement in the tty code puts it in a tricky situation, as the tty code > is not MPSAFE. Right now the strategy for the next two weeks is as follows: > > - Locking for IPX over IP will go into CVS or, if I still can't find any > testers, IPX over IP support will be removed. Note that normal IPX/SPX > support is unaffected, as that has been MPSAFE for some time. > > - IPv6 support for FAST_IPSEC will go into the tree, and KAME IPSEC will be > removed. > > - NET_NEEDS_GIANT shims will be removed from the tree. > > - i4b, netatm, and ng_h4 will be disconnected from the build, but not > deleted. Just a comment: Aswell as there is a new USB stack, there is also new I4B stack done by me: http://www.turbocat.net/~hselasky/isdn4bsd --HPS