From owner-freebsd-stable@FreeBSD.ORG Sun Jan 24 20:55:08 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FDDF106566C for ; Sun, 24 Jan 2010 20:55:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-qy0-f201.google.com (mail-qy0-f201.google.com [209.85.221.201]) by mx1.freebsd.org (Postfix) with ESMTP id 41FFD8FC16 for ; Sun, 24 Jan 2010 20:55:08 +0000 (UTC) Received: by qyk39 with SMTP id 39so1579183qyk.27 for ; Sun, 24 Jan 2010 12:55:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=uk7cMPVfhIxy3ZS1yZELFJcWtMVaT50cPAuCfle7iME=; b=Mr3o4L0j/0D+4Fe6vCem3ra5/4R1lVjHTBve/92J/m1GPhiHjTumCpCXXfbQux43Zd Oab8OksZ9I/lesG8DB3JgwXFpO5Axs3RvzNDMMM12QoamgsKX5exShg7mXnyaTY2fY8N OdlozdxjzIesVQv8nmEkJj4vcmKWxfLnsqq1I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=ldgzOA/WKfFsuPUQ3RZ29P0ss6jzo5VmaqTGNZUUVVtm2x7s3sFyKuI/nCxynKDQJL vDTatHCYjUf0PnRmUz4GcVrSjWTkb6OoFRb9QKV9fD/H8WfKy6g3K3fCozrGVsPtaR8f SvVswIzH5cDewqJxloeD0oI1uSe+PWcHkEUCQ= Received: by 10.229.102.165 with SMTP id g37mr1695256qco.65.1264366507259; Sun, 24 Jan 2010 12:55:07 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 20sm2248791qyk.1.2010.01.24.12.55.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 24 Jan 2010 12:55:06 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sun, 24 Jan 2010 12:55:05 -0800 From: Pyun YongHyeon Date: Sun, 24 Jan 2010 12:55:05 -0800 To: "Emanuele A. Bagnaschi" Message-ID: <20100124205505.GB1187@michelle.cdnetworks.com> References: <20100124183911.GA2589@polaris> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100124183911.GA2589@polaris> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD-STABLE Mailing List Subject: Re: Problematic network performance with Marvell 8072 on HP Probook 4710s X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2010 20:55:08 -0000 On Sun, Jan 24, 2010 at 07:39:11PM +0100, Emanuele A. Bagnaschi wrote: > Hi, > I've been experiencing a troubling issue with a Marvell 8072 NIC on an HP > ProBook 4710s. > I first noticed that there is a problem while transferring some files > through scp to a FreeBSD8-STABLE server: CPUs usage sky-rocketed to 100% (system) > and network performance was awful (about 1.8 MiB/s). > I tried and succeeded in reproducing the issue with 'ttcp'. I decided > to use this little benchmark because is so simple (it is linked only against libc) that I can > be sure that the problem doesn't depend on scp/ssh or other parts of the system. > Last time I checked ttcp, it was broken with threading. So you have to build ttcp without threading support or use netperf to check performance numbers. > This is the output of 'uname -a': > > FreeBSD polaris 8.0-STABLE FreeBSD 8.0-STABLE #24: Sun Jan 17 21:08:02 > CET 2010 toor@polaris:/usr/obj/usr/src/sys/POLARIS amd64 > > Here it's some relevant information to identify the NIC: > > first from 'dmesg' > > mskc0: port 0x2000-0x20ff mem > 0x90100000-0x90103fff irq 17 at device 0.0 on pci134 > msk0: on mskc0 > msk0: Ethernet address: 00:25:b3:52:fc:fa > miibus0: on msk0 > mskc0: [FILTER] > msk0: link state changed to DOWN > msk0: link state changed to UP > > and then from 'pciconf -lv' > > mskc0@pci0:134:0:0: class=0x020000 card=0x3074103c chip=0x436c11ab > rev=0x10 hdr=0x00 > vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > device = 'Marvell 8072 Ethernet Nic (88E8072)' > class = network > subclass = ethernet > > Here it's the output of 'ifconfig': > > msk0: flags=8843 metric 0 mtu > 1500 > options=19b > ether 00:25:b3:52:fc:fa > inet 192.168.1.4 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > satus: active > > > Attached you will find the results of my tests, I hope that the file > will be self-explanatory. > It seems you have Yukon Extreme controller and its revision is B0 which is known to have various silicon bug. How about disabling TX related offloading?(e.g. ifconfig msk0 -txcsum -tso) Does that make any difference? > I'm wondering, are there any other tunable parameters (apart from MSI on/off) I > should try to modify? Should I file a PR? Are there any other interesting data > I should gather? With the proper guide I'm also available to contribute some > code myself. > Given that high rates of silicon bug of Yukon having a detailed errata information would be great help to analyze the issue. But we still have no access to the information as well as datasheet.