Date: Fri, 16 May 2003 11:34:58 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.org> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/fxp if_fxp.c Message-ID: <Pine.NEB.3.96L.1030516113432.24024N-100000@fledge.watson.org> In-Reply-To: <3EC4FBB7.6060201@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 May 2003, Daniel C. Sobral wrote: > > Add a tunable/sysctl "hw.fxp_noflow" which disables flow control support > > on if_fxp cards. When flow control is enabled, if the operating system > > doesn't acknowledge the packet buffer filling, the card will begin to > > generate ethernet quench packets, but appears to get into a feedback > > loop of some sort, hosing local switches. This is a temporary workaround > > for 5.1: the ability to configure flow control should probably be > > exposed by some or another management interface on ethernet link layer > > devices. > > Looks like a mediaopt candidate to me. Though mediaopt is usually only > used for half/full-dulpex, there's the "link0" specification on some > cards that does something different. > > Alas, all the interface "capabilities" ought to be tweakable in some > standard fashion. For instance, why are special words for txcsum and > txcsum, when there's also vlan-tagging support and other capabilities > that could be set/unset from a single place? > > I'm in favor of mediaopt/-mediaopt, but... <shrug> Sounds reasonable to me. Got a patch? :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1030516113432.24024N-100000>