From owner-freebsd-fs@FreeBSD.ORG Thu Oct 25 17:17:52 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC8D2D46 for ; Thu, 25 Oct 2012 17:17:52 +0000 (UTC) (envelope-from lists@yamagi.org) Received: from mail.yamagi.org (mail.yamagi.org [IPv6:2a01:4f8:121:2102:1::7]) by mx1.freebsd.org (Postfix) with ESMTP id 590F28FC08 for ; Thu, 25 Oct 2012 17:17:52 +0000 (UTC) Received: from happy.home.yamagi.org (hmbg-4d06f908.pool.mediaWays.net [77.6.249.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yamagi.org (Postfix) with ESMTPSA id A384E1666312; Thu, 25 Oct 2012 19:17:50 +0200 (CEST) Date: Thu, 25 Oct 2012 19:17:45 +0200 From: Yamagi Burmeister To: pyunyh@gmail.com Subject: Re: Can not read from ZFS exported over NFSv4 but write to it Message-Id: <20121025191745.7f6a7582d4401de467d3fe18@yamagi.org> In-Reply-To: <20121025180344.GC3267@michelle.cdnetworks.com> References: <20121023204623.a1eef4f99b5f786050229b6c@yamagi.org> <1579346453.2736080.1351029315835.JavaMail.root@erie.cs.uoguelph.ca> <20121024213602.b727c557f0332f28a66f87cc@yamagi.org> <20121025180344.GC3267@michelle.cdnetworks.com> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Thu__25_Oct_2012_19_17_45_+0200_cvMMz+uEE_Kf6=kL" Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2012 17:17:53 -0000 --Signature=_Thu__25_Oct_2012_19_17_45_+0200_cvMMz+uEE_Kf6=kL Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello :) On Thu, 25 Oct 2012 11:03:44 -0700 YongHyeon PYUN wrote: > age(4) is cheap and consumer grade controller but it shows > good performance on various network loads. It's much better choice > than using other cheap controllers. >=20 > Would you show me dmesg output(age(4) and atphy(4) only)? > And try disabling TSO or TX checksum offloading and see whether > that makes any difference. > I remember age(4) had a 64bit DMA bug but it was fixed long > time ago. Yeah I was the one who reported it. This is the same machine... If disabled TSO and it seems to work. I've copied ~10GB from the client to the server and the other way round without any problem. The dmesg (with verbose boot enabled) is: age0: mem 0xfeac0000-0xfeafffff irq 18 at device 0.0 on pci2 age0: PCI device revision : 0x00b0 age0: Chip id/revision : 0x9006 age0: 1280 Tx FIFO, 2364 Rx FIFO age0: MSIX count : 0 age0: MSI count : 1 age0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 256 to local APIC 0 vector 48 age0: using IRQ 256 for MSI age0: Using 1 MSI messages. age0: Read request size : 512 bytes. age0: TLP payload size : 128 bytes. age0: 4GB boundary crossed, switching to 32bit DMA addressing mode. age0: PCI VPD capability not found! miibus0: on age0 atphy0: PHY 0 on miibus0 atphy0: OUI 0x00c82e, model 0x0001, rev. 5 atphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto age0: bpf attached age0: Ethernet address: 00:23:54:31:a0:12 pci3: driver added age0: link state changed to DOWN age0: interrupt moderation is 100 us. age0: link state changed to UP Ciao, Yamagi --=20 Homepage: www.yamagi.org XMPP: yamagi@yamagi.org GnuPG/GPG: 0xEFBCCBCB --Signature=_Thu__25_Oct_2012_19_17_45_+0200_cvMMz+uEE_Kf6=kL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlCJdD0ACgkQWTjlg++8y8tx1ACfdN/wQaAegdwxCMISn1/0KAFP YjoAn0+bquUz/FNazSsLKw+e1JeMuUAk =SY0g -----END PGP SIGNATURE----- --Signature=_Thu__25_Oct_2012_19_17_45_+0200_cvMMz+uEE_Kf6=kL--