From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 17:30:35 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85C3016A424; Wed, 15 Mar 2006 17:30:35 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 704A043D7E; Wed, 15 Mar 2006 17:30:24 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k2FHT01N011656; Wed, 15 Mar 2006 10:29:09 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 15 Mar 2006 10:29:03 -0700 (MST) Message-Id: <20060315.102903.08650855.imp@bsdimp.com> To: Alexander@Leidinger.net From: "M. Warner Losh" In-Reply-To: <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> References: <20060314.204252.74651890.imp@bsdimp.com> <20060315105031.E5861@fledge.watson.org> <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 15 Mar 2006 10:29:10 -0700 (MST) Cc: arch@freebsd.org, rwatson@freebsd.org, hselasky@c2i.net Subject: Re: netatm: plan for removal unless an active maintainer is found X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Mar 2006 17:30:35 -0000 In message: <20060315151058.c85pw3x14wkkk8g0@netchild.homeip.net> Alexander Leidinger writes: : Robert Watson wrote: : : > The other large chunk of non-MPSAFE network device driver and stack : > code, FYI, is the i4b code. In principle, a newly added committed is : : The USB stack is also a part of the problem (USB network interfaces), I : think. It definitely is a problem. And I didn't list any usb interfaces as not being MPSAFE. : > now available to work on the capi integration, and hopefully will do : > the SMP safety work as part of that. If not, it's also on the : > chopping block. It's a significant piece of otherwise unmaintained : > code, and something that's not trivially testable (at least, not by : > me or anyone I've talked to lately :-). I don't want to see it leave : > the tree, but it needs to be updated so that it can run MPSAFE before : > 7.0. : : I may add, that Hans-Petter Selasky has a MPSAFE replacement (written from : scratch it seems) for I4B (AFAIK including capi) and the USB stack. I have : tested or reviewed neither of them, but as far as I can read in the : mailinglists, he adresses not only the issues you mention here, but he also : provides bugfixes and additional features compared to our current code base. The problem is that this code isn't busdma safe at the moment. It was posted for review on the NetBSD lists and this was the biggest set of comments on tech-kern@netbsd.org. Since it isn't busdma safe, we'd lose usb on sparc64 (and maybe arm) when this code is brought into the tree. There have also been signficant concerns about the locking that's done in the code as well, but I've not reviewed it recently. There's been a lot of work done here, and that work is generally good, but last time I looked at the code it wasn't ready to be integrated to the tree. Warner