From owner-freebsd-current@FreeBSD.ORG Sun Jul 15 10:40:41 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF62416A402; Sun, 15 Jul 2007 10:40:41 +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 9A1A613C471; Sun, 15 Jul 2007 10:40:41 +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 D0263490C6; Sun, 15 Jul 2007 06:40:40 -0400 (EDT) Date: Sun, 15 Jul 2007 11:40:40 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Doug Barton In-Reply-To: <4699A1A1.8070603@FreeBSD.org> Message-ID: <20070715113916.M91807@fledge.watson.org> References: <20070714181315.V67691@fledge.watson.org> <4699A1A1.8070603@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: Re: HEADS UP: netatm disabling taking place shortly 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: Sun, 15 Jul 2007 10:40:41 -0000 On Sat, 14 Jul 2007, Doug Barton wrote: > This is cool stuff, thanks for your dogged persistence in eliminating GIANT > from the network stack! > > One tiny thing I've noticed doing a buildworld tonight, because of the way > that /usr/src/usr.bin/kdump/mkioctls works (starting at line 19) it's > necessary to remove /usr/include/netatm _before_ trying to build. You might > want to include that in any instructions you send out regarding this change > (and maybe in UPDATING). If I've missed where you've said that already, > sorry for the noise. It's odd, actually -- I ran into this a couple of times earlier in preparing the patch, but didn't run into it with later versions after I redid the include things, etc. For example, on a vanilla machine (from a couple of weeks ago) now, I don't see the problem during buildworld. Obviously, a bit more debugging is called for. Could you try removing the tree in /usr/obj and see if that helps? Perhaps things are lasting between build runs... Robert N M Watson Computer Laboratory University of Cambridge