From owner-freebsd-arch@FreeBSD.ORG Wed Mar 15 17:15:19 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 DD6B016A466; Wed, 15 Mar 2006 17:15:19 +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 1AD1243D67; Wed, 15 Mar 2006 17:15:19 +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 k2FHDbQm011534; Wed, 15 Mar 2006 10:13:38 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 15 Mar 2006 10:13:39 -0700 (MST) Message-Id: <20060315.101339.45743485.imp@bsdimp.com> To: harti@freebsd.org, hartmut.brandt@dlr.de From: "M. Warner Losh" In-Reply-To: <20060315090615.I56469@beagle.kn.op.dlr.de> References: <20060315004530.B5861@fledge.watson.org> <20060314.204252.74651890.imp@bsdimp.com> <20060315090615.I56469@beagle.kn.op.dlr.de> 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:13:39 -0700 (MST) Cc: arch@freebsd.org, rwatson@freebsd.org 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:15:20 -0000 In message: <20060315090615.I56469@beagle.kn.op.dlr.de> Harti Brandt writes: : On Tue, 14 Mar 2006, Warner Losh wrote: : : WL>> The main motivator for pruning has to do with the SMP network stack work: : WL>> we're reaching the point, discussed on a number of occasions previously on : WL>> this mailing list, where jettisoning unmaintained network stack components : WL>> that are unable to run MPSAFE, is highly desirable. : WL> : WL>What's the timeline for non-MPSAFE network drivers to be taken out : WL>behind the woodshed? Right now the list appears to be: : WL> : WL> an, awi, cm, cnw, cs, en, ex, fatm, ie, lnc, patm, fea, fpa, : WL> mn, ray, sbni, sbsh, snc, tx, wl, xe, ar, sr, plip : : Both patm and fatm are MPSAFE - I forgot, maybe, to set the INTR_MPSAFE : flag. I'll fix that. I might have missed something when I came up with the list. Warner