From owner-freebsd-current@FreeBSD.ORG Thu Jan 26 00:13:15 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 084E516A420; Thu, 26 Jan 2006 00:13:15 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id A62DF43D45; Thu, 26 Jan 2006 00:13:14 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k0Q0DBo7067024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 25 Jan 2006 16:13:11 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43D8147C.5080609@errno.com> Date: Wed, 25 Jan 2006 16:14:52 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <20060124075437.B67285@xorpc.icir.org> <43D67C6E.7020403@errno.com> <43D6811D.9070309@elischer.org> <20060124.231504.74682748.sthaug@nethelp.no> <20060124223539.GH69162@funkthat.com> <20060125104901.X70912@fledge.watson.org> In-Reply-To: <20060125104901.X70912@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: rizzo@icir.org, John-Mark Gurney , julian@elischer.org, sthaug@nethelp.no, current@freebsd.org Subject: Re: if_flags usage etc. 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: Thu, 26 Jan 2006 00:13:15 -0000 Robert Watson wrote: > > On Tue, 24 Jan 2006, John-Mark Gurney wrote: > >> sthaug@nethelp.no wrote this message on Tue, Jan 24, 2006 at 23:15 +0100: >> >>>> We should probably better document the interface "interface". if we are >>>> going to (as Sam suggests) >>>> do some cleanups we might as well consider what other changes should be >>>> put in at the same time. >>> >>> >>> A couple of other suggestions: >>> >>> - For software routers (quagga, zebra etc.) it would be very nice to >>> have "link up" / "link down" notifications to the routing process(es). >> >> >> already supported, either through kqueue, routing socket, or devd (I >> believe)... > > > However, I believe some interface drivers don't generate these events. > Drivers not supporting a specific event delivered by an interrupt > probably need to learn to poll for state changes so that they can > generate an event. I am not aware of any drivers that do not generate the events; only drivers that do not properly detect link status changes. Sam