From owner-cvs-src@FreeBSD.ORG Fri May 16 08:35:23 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 3916D37B401; Fri, 16 May 2003 08:35:23 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DA4243FA3; Fri, 16 May 2003 08:35:20 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h4GFYwOn032551; Fri, 16 May 2003 11:34:58 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h4GFYwvA032548; Fri, 16 May 2003 11:34:58 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 16 May 2003 11:34:58 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Daniel C. Sobral" In-Reply-To: <3EC4FBB7.6060201@tcoip.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 15:35:23 -0000 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... Sounds reasonable to me. Got a patch? :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories