From owner-freebsd-current@FreeBSD.ORG Wed Mar 29 10:11:59 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 074AC16A400 for ; Wed, 29 Mar 2006 10:11:59 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7221E43D53 for ; Wed, 29 Mar 2006 10:11:58 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id CF77246B2C for ; Wed, 29 Mar 2006 05:11:57 -0500 (EST) Date: Wed, 29 Mar 2006 10:11:57 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org In-Reply-To: <20060317141627.W2181@fledge.watson.org> Message-ID: <20060329100839.V19236@fledge.watson.org> References: <20060317141627.W2181@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: REMINDER: Re: HEADS UP: network stack and socket hackery over the next few weeks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2006 10:11:59 -0000 On Fri, 17 Mar 2006, Robert Watson wrote: > Over the next few weeks, I'll be doing a fairly serious workworking of the > socket and protocol reference models, in order to clean up a number of > long-standing race conditions and provide infrastructure for significant > locking optimizations for several protocols (including TCP). This is high > risk work, in that this part of the socket code is very complex and there > are a great many subtleties. Part of the goal of the work is to eliminate > some of this complexity, and make the subtle a bit more obvious (and > documented), so I think it's all for the good in the long term. However, it > will likely introduce significant instability in the short term, especially > in the TCP code where there will be substantial changes in the memory > management model. > > I've started merging minor parts of the patch over the last few days, but > things will get serious around April 1 when the deadline for maintenance on > the netatm stack expires (see arch@ and net@ posts about this), allowing me > to bring in changes that are not known to work with netatm. As such, be > warned that things may get a bit messy! As a reminder, April 1 is now three days away. On April 1, I will be committed an extensive set of socket and netinet changes which will likely render the network stack broken. I say this with some confidence because I have tested the changes fairly extensively, as have a number of other developers, and they appear to mostly work. Therefore, they will be broken :-). I will be posting updated versions of these patches shortly, but unless we run into show-stopper serious instability with them, rather than nits, I will commit them (in their updated form) on April 1 shortly after the netatm build is disabled. I will post another HEADS UP as the changes go into the tree, and will be monitoring things closely to try and get any bugs that might turn up fixed as quickly as possible. As an FYI, I will be travelling the weeks of April 6 - April 21, but will be online frequently, and working for several days in the Bay Area during the trip. Please report bugs relating to this work to current@. Robert N M Watson