From owner-cvs-src@FreeBSD.ORG Fri May 16 07:55:08 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92A7137B401; Fri, 16 May 2003 07:55:08 -0700 (PDT) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B340843FAF; Fri, 16 May 2003 07:55:02 -0700 (PDT) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h4GEsx932295; Fri, 16 May 2003 11:54:59 -0300 Message-ID: <3EC4FBB7.6060201@tcoip.com.br> Date: Fri, 16 May 2003 11:54:47 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: Robert Watson References: <200305160113.h4G1DHqN090638@repoman.freebsd.org> In-Reply-To: <200305160113.h4G1DHqN090638@repoman.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/fxp if_fxp.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2003 14:55:08 -0000 Robert Watson wrote: > rwatson 2003/05/15 18:13:17 PDT >=20 > FreeBSD src repository >=20 > Modified files: > sys/dev/fxp if_fxp.c=20 > Log: > Add a tunable/sysctl "hw.fxp_noflow" which disables flow control supp= ort > on if_fxp cards. When flow control is enabled, if the operating syst= em > 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 workar= ound > for 5.1: the ability to configure flow control should probably be > exposed by some or another management interface on ethernet link laye= r > devices. Looks like a mediaopt candidate to me. Though mediaopt is usually only=20 used for half/full-dulpex, there's the "link0" specification on some=20 cards that does something different. Alas, all the interface "capabilities" ought to be tweakable in some=20 standard fashion. For instance, why are special words for txcsum and=20 txcsum, when there's also vlan-tagging support and other capabilities=20 that could be set/unset from a single place? I'm in favor of mediaopt/-mediaopt, but... --=20 Daniel C. Sobral Ger=EAncia de Opera=E7=F5es Divis=E3o de Comunica=E7=E3o de Dados Coordena=E7=E3o de Seguran=E7a 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