Date: Thu, 26 Jan 2006 21:09:57 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: rwatson@freebsd.org Cc: rizzo@icir.org, gurney_j@resnet.uoregon.edu, julian@elischer.org, sthaug@nethelp.no, current@freebsd.org Subject: Re: if_flags usage etc. Message-ID: <20060126.210957.112636931.imp@bsdimp.com> In-Reply-To: <20060125104901.X70912@fledge.watson.org> References: <20060124.231504.74682748.sthaug@nethelp.no> <20060124223539.GH69162@funkthat.com> <20060125104901.X70912@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20060125104901.X70912@fledge.watson.org>
Robert Watson <rwatson@freebsd.org> writes:
:
: 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.
Most of the problem is that mii_tick doesn't run when the interface is
not UP. This means they are blind to interface changes.
Really old drivers, without mii support, do need to poll for link
changes.
Really really old hardware, like ne-2000, can't even poll for link
changes. You know the link is up/down based on errors or success of
last packet...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060126.210957.112636931.imp>