From owner-freebsd-arch@FreeBSD.ORG Mon Jun 30 12:36:46 2008 Return-Path: Delivered-To: arch@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34EA61065672; Mon, 30 Jun 2008 12:36:46 +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 0A1D28FC1B; Mon, 30 Jun 2008 12:36:46 +0000 (UTC) (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 AA10446B2E; Mon, 30 Jun 2008 08:36:45 -0400 (EDT) Date: Mon, 30 Jun 2008 13:36:45 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Alexander Leidinger In-Reply-To: <20080630141611.56172qs6gac45ri8@webmail.leidinger.net> Message-ID: <20080630133335.K54631@fledge.watson.org> References: <20080524111715.T64552@fledge.watson.org> <20080629180126.F90836@fledge.watson.org> <20080630091033.P3968@fledge.watson.org> <20080630141611.56172qs6gac45ri8@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org, current@FreeBSD.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (fwd)) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2008 12:36:46 -0000 On Mon, 30 Jun 2008, Alexander Leidinger wrote: >> Here's the revised list of drivers that will have their build disabled in >> the next week (subject to an appropriate block of time for me): > > Is this list supposed to be complete (including dependencies)? bktr uses > some I2C stuff and cxm (in ports) too. As far as I'm aware, this list is complete. I compiled it by identifying all network device drivers that set (or may set) the IFF_NEEDSGIANT. With respect to i2c, this refers *only* to the if_ic.c network device driver, and not the other services associated with i2c, so bktr and other i2c consumers should be unaffected. I'm not familiar with cxm so can't comment on that. If you are aware of any other in-tree network device drivers that use IFF_NEEDSGIANT and aren't on the list, please do let me know. Robert N M Watson Computer Laboratory University of Cambridge