Date: Fri, 16 May 2003 11:54:47 -0300 From: "Daniel C. Sobral" <dcs@tcoip.com.br> To: Robert Watson <rwatson@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/fxp if_fxp.c Message-ID: <3EC4FBB7.6060201@tcoip.com.br> In-Reply-To: <200305160113.h4G1DHqN090638@repoman.freebsd.org> References: <200305160113.h4G1DHqN090638@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > rwatson 2003/05/15 18:13:17 PDT > > FreeBSD src repository > > Modified files: > sys/dev/fxp if_fxp.c > Log: > 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> -- Daniel C. Sobral Gerência de Operações Divisão de Comunicação de Dados Coordenação de Segurança VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EC4FBB7.6060201>