From owner-freebsd-net@FreeBSD.ORG Fri Jun 11 18:09:20 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C92381065678 for ; Fri, 11 Jun 2010 18:09:20 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [204.109.60.94]) by mx1.freebsd.org (Postfix) with ESMTP id AEE038FC0A for ; Fri, 11 Jun 2010 18:09:20 +0000 (UTC) Received: from unknown (87-194-158-129.bethere.co.uk [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 70EAA5CCC for ; Fri, 11 Jun 2010 17:51:45 +0000 (UTC) Date: Fri, 11 Jun 2010 18:51:03 +0100 From: Bruce Cran To: freebsd-net@freebsd.org Message-ID: <20100611185103.000026a3@unknown> X-Mailer: Claws Mail 3.7.4cvs1 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Testing recent sis(4) changes on SiS controllers X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jun 2010 18:09:20 -0000 I recently committed to 9-CURRENT a fix for the sis(4) driver to improve performance when the host can't keep up with the processing requirements of the network. Previously, when an overflow occurred the chip was reset and a sleep of 100ms was introduced while programming a short cable fix for the NatSemi FA311 chip. Now, the reset is only done once when a media change occurs and the delay was reduced to 100us. However there's some doubt as to whether the change may cause problems on SiS based controllers as found on some motherboards - they may require the chip to be reset when an overflow occurs. If anyone has a machine with a SiS based controller I'd welcome any testing that could be done to check that I've not broken overflow handling. Overflows are indicated by the Ierrs column in the output of "netstat -s". -- Bruce Cran