From owner-freebsd-current@FreeBSD.ORG Wed Jan 25 10:54:30 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 BA17F16A427 for ; Wed, 25 Jan 2006 10:54:30 +0000 (GMT) (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 6BC7543F1C for ; Wed, 25 Jan 2006 10:49:51 +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 47F0146C64; Wed, 25 Jan 2006 05:48:43 -0500 (EST) Date: Wed, 25 Jan 2006 10:50:06 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: John-Mark Gurney In-Reply-To: <20060124223539.GH69162@funkthat.com> Message-ID: <20060125104901.X70912@fledge.watson.org> References: <20060124075437.B67285@xorpc.icir.org> <43D67C6E.7020403@errno.com> <43D6811D.9070309@elischer.org> <20060124.231504.74682748.sthaug@nethelp.no> <20060124223539.GH69162@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: rizzo@icir.org, 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: Wed, 25 Jan 2006 10:54:31 -0000 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. Robert N M Watson