From owner-freebsd-net@FreeBSD.ORG Sat Dec 4 07:49:00 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 60157106566B for ; Sat, 4 Dec 2010 07:49:00 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 18AA18FC16 for ; Sat, 4 Dec 2010 07:49:00 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id oB47mwvZ019559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 Dec 2010 23:48:58 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id oB47mw7M019558; Fri, 3 Dec 2010 23:48:58 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA26208; Fri, 3 Dec 10 23:36:45 PST Date: Fri, 03 Dec 2010 23:36:17 -0800 From: perryh@pluto.rain.com To: egrosbein@rdtc.ru, jfvogel@gmail.com Message-Id: <4cf9ef71./9OtjLOA2+IV0UUh%perryh@pluto.rain.com> References: <201011270946271408828@yahoo.com.cn> <20101128081617.GA90332@zibbi.meraka.csir.co.za> <4CF73A2C.7000802@rdtc.ru> <4CF89EE7.8020807@rdtc.ru> <4CF93A77.30804@rdtc.ru> <4CF9470F.4020709@sentex.net> <4CF947D4.10504@rdtc.ru> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, mike@sentex.net Subject: Re: Problem with igb(4) updated to version 2.0.7 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: Sat, 04 Dec 2010 07:49:00 -0000 Jack Vogel wrote: > There are pros and cons either way you do things. I was talking > to some of our Linux crew, they recently changed things so it > would shut down the phy, but that doesn't always make everyone > happy either. In particular, depending on the type of switch and how it is configured, it may take 30 seconds or so after link is restored for the switch to do spanning-tree validation before it will start to pass traffic. There may be something to be said for making the driver's behavior configurable.