Date: Wed, 15 Mar 2006 10:13:39 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: harti@freebsd.org, hartmut.brandt@dlr.de Cc: arch@freebsd.org, rwatson@freebsd.org Subject: Re: netatm: plan for removal unless an active maintainer is found Message-ID: <20060315.101339.45743485.imp@bsdimp.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20060315090615.I56469@beagle.kn.op.dlr.de>
Harti Brandt <hartmut.brandt@dlr.de> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060315.101339.45743485.imp>