From owner-freebsd-net@FreeBSD.ORG Wed Jul 28 22:45:52 2010 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E732A1065672; Wed, 28 Jul 2010 22:45:52 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C50A28FC0C; Wed, 28 Jul 2010 22:45:52 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 67DC046B45; Wed, 28 Jul 2010 18:45:52 -0400 (EDT) Date: Wed, 28 Jul 2010 23:45:52 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: freebsd-net@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: freebsd-arch@FreeBSD.org Subject: Future of netnatm: volunteer wanted -- and/or -- removal notice X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2010 22:45:53 -0000 Dear all: When the new link layer framework was introduced in 8.0, one of our ATM stacks, netnatm, was left behind. As a result, it neither compiles nor runs in 8.x and 9.x. This e-mail serves two purposes: (1) To solicit a volunteer who can work on the netnatm stack in 9.x, with potential merge to 8.x, to get it back to functionality before 9.0 ships. This is the preferred course of action. (2) To serve as notice that if we can't find a volunteer to do this, we will remove netnatm and associated parts from the tree in 9.0 since they'll have gone one major version neither compiling nor running. This is the fallback plan. I'm in no great rush to remove netnatm, having spent quite a bit of time making it work in our MPSAFE world order a couple of years ago. However, the code is bitrotting and requires urgent attention if it's going to work again easily (the stack is changing around it, and because netnatm doesn't build, it will get only cursory and likely incorrect updates). I'm happy to help funnel changes into the tree from non-committers, as well as answer questions about the network stack, but I have no hardware facilities for debugging or testing netnatm changes myself, nor, unfortunately, the time to work on the code. In order to provide further motivation for potentially interested parties, here's the proposed six-month removal schedule: 28 July 2010 - Notice of proposed removal 28 October 2010 - Transmit of notice of proposed removal 28 January 2011 - Proposed removal date This schedule may be updated as the 9.0 release schedule becomes more clear, or if there are obvious signs of improvement and just a couple more months would get it fixed :-). And, if worst comes to worst and we can't find a volunteer, the code will live on in the source repository history if there's a desire to rejuvenate it in the future. Thanks, Robert Robert N M Watson Computer Laboratory University of Cambridge