Date: Mon, 18 Apr 2005 09:38:37 +0200 (CEST) From: Harti Brandt <hartmut.brandt@dlr.de> To: Robert Watson <rwatson@FreeBSD.org> Cc: arch@freebsd.org Subject: Re: De-orbitting ATM-HARP Message-ID: <20050418093638.B1882@beagle.kn.op.dlr.de> In-Reply-To: <20050416154049.B64125@fledge.watson.org> References: <20050415173711.I658@beagle.kn.op.dlr.de> <20050416154049.B64125@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Apr 2005, Robert Watson wrote: RW> RW>On Fri, 15 Apr 2005, Harti Brandt wrote: RW> RW>> not sure whether this is actually off-topic. Some time ago I asked on RW>> freebsd-atm who would have a problem when we remove HARP (netatm, hfa) from RW>> 6. I got only two or three answers which said 'go for it'. Nobody said that RW>> he would have a problem. So should we do it and when? Perhaps the best time RW>> is before 6.0. That would be in the next two weeks as I understand. RW>> RW>> While there I would also remove everything from netnatm that is not needed RW>> by NgATM. This is mainly the socket interface. I'm not aware of any RW>> application that uses it. Any thoughts on this? RW> RW>One of the concerns I have with the ATM stacks present in the system is that RW>none appears to be MPSAFE. I am currently unable to perform any ATM-related RW>testing, and so don't feel comfortable starting on locking work on the ATM RW>components. If we can remove unused ATM code, that makes the overall task of RW>getting the last bits of the network stack MPSAFE much easier. NgATM is MPSAFE to the extend that netgraph is MPSAFE. The drivers I've written are MPSAFE too to the extend the interface driver framework is MPSAFE (think of calling interface routines while the driver is unloading and so on. There was some discussion about how to fix this, but it's still there). RW>BTW, have you tried pinging freebsd-net? Ok. I'll do that today. harti
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050418093638.B1882>