From owner-freebsd-net@FreeBSD.ORG Mon Nov 28 04:45:56 2011 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 219151065672 for ; Mon, 28 Nov 2011 04:45:56 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id A3CC48FC08 for ; Mon, 28 Nov 2011 04:45:55 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so9762365bkb.13 for ; Sun, 27 Nov 2011 20:45:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=81FzPsVRAUMTi9Tpy3fQq2vybTW8Gcrf3tJBA9KI38U=; b=lRVmSWOr2dwj/gyb3ioGZ4+4HraKj9kDDtHn0WMSt94FaucCvOlOxt6V8ySiU2eVSc 1jrNOCB9OSEVTkwkDdaZekcN20yYojgLK/TvCzuQRn6Jv2mRc4h36tSJ80zjnUQp3kip G/hCPtBbRbfFN8dlmMEOSvtByYkH+x8pHiHEg= Received: by 10.205.42.202 with SMTP id tz10mr5065944bkb.57.1322455554219; Sun, 27 Nov 2011 20:45:54 -0800 (PST) Received: from imba-brutale.totalterror.net ([93.152.152.135]) by mx.google.com with ESMTPS id x14sm27075998bkf.10.2011.11.27.20.45.52 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 27 Nov 2011 20:45:52 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=us-ascii From: Nikolay Denev In-Reply-To: <20111128004340.GA1830@michelle.cdnetworks.com> Date: Mon, 28 Nov 2011 06:45:52 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20111024175252.GB4663@michelle.cdnetworks.com> <0DF73F37-3E46-4F7D-AA6B-B7EB2F2276AB@gmail.com> <20111128004340.GA1830@michelle.cdnetworks.com> To: pyunyh@gmail.com X-Mailer: Apple Mail (2.1251.1) Cc: freebsd-net@freebsd.org Subject: Re: Possible sge(4)/atphy(4) regression on RELENG_9? 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: Mon, 28 Nov 2011 04:45:56 -0000 On Nov 28, 2011, at 2:43 AM, YongHyeon PYUN wrote: > On Sat, Nov 26, 2011 at 04:39:03PM +0200, Nikolay Denev wrote: >>=20 >> On Oct 24, 2011, at 9:18 PM, Nikolay Denev wrote: >>=20 >>>=20 >>> On Oct 24, 2011, at 8:52 PM, YongHyeon PYUN wrote: >>>=20 >>>> On Mon, Oct 24, 2011 at 04:43:57PM +0300, Nikolay Denev wrote: >>>>> Hello, >>>>>=20 >>>>> I've recently upgraded a box running RELENG_8 to RELENG_9 and = immediately I noticed much slower network connection. >>>>> Running iperf shows about 20-30Mbits which was almost full GigE = (~900Mbits) speed before. >>>>>=20 >>>>> I'm noticing interface errors : >>>>>=20 >>>>> [16:37]ndenev@nas:~% netstat -I sge0 >>>>> Name Mtu Network Address Ipkts Ierrs Idrop = Opkts Oerrs Coll >>>>> sge0 1500 00:0a:e4:86:62:fa 76114295 42197 0 = 103559806 10324 0 >>>>> sge0 1500 10.0.0.0 nas 76109575 - - = 119109557 - - >>>>>=20 >>>>> Both the switch and the card show 1000 full-duplex. >>>>> I've tried playing with rxcsum,txcsum,vlanhwtag,tso but disabling = even all of them do not change anything. >>>>> I've tried different switch port and changed the cable. >>>>>=20 >>>>> Here is devinfo for my hardware : >>>>>=20 >>>>> sge0 pnpinfo vendor=3D0x1039 device=3D0x0191 subvendor=3D0x103c = subdevice=3D0x2a70 class=3D0x020000 >>>>> atphy0 pnpinfo oui=3D0xc82e model=3D0x1 rev=3D0x6 at phyno=3D0 >>>>>=20 >>>>> Of course all of this can mean hardware problem, I just want to = ask if somebody is seeing something similar, since >>>>> there are quite a lot minibus related changes as far as I can see. >>>>>=20 >>>>> I'll boot RELENG_8 again tomorrow and do a quick test again to = verify that this is not a hardware issue. >>>>>=20 >>>>=20 >>>> I don't have sge(4) controller so it would be better to let us know >>>> which revision introduced the regression. Just looking over the >>>> code change didn't reveal the possible cause. >>>> BTW, I thought sge(4) shall use rgephy(4). Can you also verify >>>> whether sge(4) in stable/8 also use atphy(4)? >>>=20 >>> I've just checked my logs and I can confirm that it was atphy(4) = even in stable/8. >>>=20 >>> Sep 26 15:55:19 nas kernel: atphy0: PHY = 0 on miibus0 >>> Sep 26 15:55:19 nas kernel: atphy0: none, 10baseT, 10baseT-FDX, = 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto >>>=20 >>> I'll post more info when I try again stable/8 on this hardware. >>>=20 >>> Thanks! >>>=20 >>=20 >> Just for the sake of completeness I'm reporting that the problem = turned out to be not hardware related. >> The thread "TCP Reassembly Issues" in freebsd-stable list describes = the issue. >>=20 >=20 > Thanks for letting us know that. >=20 > BTW, it seems sge(4) controllers support flow control as well as > jumbo frame by scattering incoming jumbo frame into multiple RX > buffers. Jumbo frame support code may require more time in my side > but flow control support code could be implemented within a week. > Can you test the patch if I manage to write support code? Yes, I can test it, my switch supports both flow control and jumbo = frames. Thanks, Nikolay=