From owner-freebsd-stable@FreeBSD.ORG Mon Nov 8 21:41:14 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78FF6106564A for ; Mon, 8 Nov 2010 21:41:14 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2001:470:9a47::1]) by mx1.freebsd.org (Postfix) with ESMTP id 27D2D8FC14 for ; Mon, 8 Nov 2010 21:41:14 +0000 (UTC) Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1]) by acme.spoerlein.net (8.14.4/8.14.4) with ESMTP id oA8LfC6F031725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Nov 2010 22:41:13 +0100 (CET) (envelope-from uqs@spoerlein.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=spoerlein.net; s=dkim200908; t=1289252473; bh=DdJjqnSUGzFWP+q6vfU+q5jyKqlsDl2GWHUt27CESiE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=UIL6CReG8PjbbdNLhJlhh+kCxcTWdGaXxmpfUt6tjoAEwWdjbPjQ6e2kdWc7nV8vL GNwxNp14zBCCZmoXfKvi9XwbRdyxKPEgfTikn0N3Vjd5pSa19V+lPrd1p44rCCVaQs 5eVOzzsWpI7QcYVqJWSHAQq49d61YODTqaoEZit0= Received: (from uqs@localhost) by acme.spoerlein.net (8.14.4/8.14.4/Submit) id oA8LfC4M031724; Mon, 8 Nov 2010 22:41:12 +0100 (CET) (envelope-from uqs@spoerlein.net) Date: Mon, 8 Nov 2010 22:41:12 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Pyun YongHyeon Message-ID: <20101108214112.GY85693@acme.spoerlein.net> Mail-Followup-To: Pyun YongHyeon , stable@freebsd.org References: <20101106093700.GW85693@acme.spoerlein.net> <20101107112421.GH85693@acme.spoerlein.net> <20101107231020.GB1279@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101107231020.GB1279@michelle.cdnetworks.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org Subject: Re: Abysmal re(4) performance under 8.1-STABLE (mid-August) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2010 21:41:14 -0000 On Sun, 07.11.2010 at 15:10:20 -0800, Pyun YongHyeon wrote: > On Sun, Nov 07, 2010 at 12:24:21PM +0100, Ulrich Sp??rlein wrote: > > On Sat, 06.11.2010 at 23:19:33 -0700, Pyun YongHyeon wrote: > > > On Sat, Nov 6, 2010 at 2:37 AM, Ulrich Sp??rlein wrote: > > > > Hello Pyun, > > > > > > > > On this new server, I cannot get more than ~280kByte/s up/downstream out of > > > > re(4) without any tweaking. > > > > > > > > re0: flags=8843 metric 0 mtu 1500 > > > > ?? ?? ?? ??options=389b > > > > ?? ?? ?? ??ether 00:21:85:63:74:34 > > > > ?? ?? ?? ??inet6 fe80::221:85ff:fe63:7434%re0 prefixlen 64 scopeid 0x1 > > > > ?? ?? ?? ??inet 46.4.12.147 netmask 0xffffffc0 broadcast 46.4.12.191 > > > > ?? ?? ?? ??nd6 options=3 > > > > ?? ?? ?? ??media: Ethernet autoselect (100baseTX ) > > > > ?? ?? ?? ??status: active > > > > > > > > > > It seems the link was resolved to half-duplex. Does link partner > > > also agree on the resolved speed/duplex? > > > > As this is a dedicated server in a colo hundreds of km away, I have no > > means to check this easily. Especially I cannot change the setting from > > auto-neg. Btw, linux will show a negotiated 100/full link via mii-tool. > > > > I guess you can contact network administrator of the data center to > check the switch configuration. IEEE 802.3 says if link parter use > forced full-duplex media and you use auto media, the resolved > duplex is half-duplex by definition. I think RealTek may have > followed the standard. There is no reason to use manual media > configuration unless your link partner is severely broken with > auto-negotiation. > > Due to silicon bug of RealTek PHYs, rgephy(4) always use > auto-negotiation so manual media configuration is a kind of > auto-negotiation with limited set of available media advertising. > I don't know how Linux solve the silicon bug though. One of magic > DSP fixups might fix the issue, the DSP fixups vendor released is > not under BSD license and does not say more detailed information > for the code. Luckily the provider switch me to another switch that is set to autoneg, instead of hardcoded to 100/full. re(4) now happily transfers with reasonable speeds, ie. 11MByte/s. Thanks! Uli