From owner-freebsd-net@FreeBSD.ORG Wed Feb 25 01:26:02 2009 Return-Path: Delivered-To: net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED44F106564A; Wed, 25 Feb 2009 01:26:02 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id C0F738FC08; Wed, 25 Feb 2009 01:26:02 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id BD7512A5603; Tue, 24 Feb 2009 20:09:33 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 24 Feb 2009 20:09:33 -0500 X-Sasl-enc: E+qYKlzQt+kpEytPN729kt4y0u1+PwXbQPMYISlYCrdq 1235524171 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 3321430D7F; Tue, 24 Feb 2009 20:09:31 -0500 (EST) Message-ID: <49A49A4A.4030902@incunabulum.net> Date: Wed, 25 Feb 2009 01:09:30 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Robert Watson References: <20080526110543.J26343@fledge.watson.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org, net@FreeBSD.org Subject: Re: HEADS UP: IFF_NEEDSGIANT consumers to be disabled, removed 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, 25 Feb 2009 01:26:03 -0000 Robert Watson wrote: > > .. > Just a reminder that 1 March is gradually approaching. It looks like > the new USB stack is settling nicely, so I currently have no plans to > defer the above schedule. Just to say: this is good news for 8.x, particularly for VIMAGE. Losing the Giant lock from the network drivers will resolve the possibility of a number of race conditions occurring in the network stack, which are particularly noticeable with VIMAGE, due to how protocol domains attach within vimages.. I'd expect that ongoing work could benefit by eliminating some use of netisrs, however, it might be a good idea to retain those for a little longer to make backporting to 7.x easier. thanks, BMS