From owner-freebsd-stable@FreeBSD.ORG Thu Sep 27 06:53:52 2007 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 91AF516A418 for ; Thu, 27 Sep 2007 06:53:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.237]) by mx1.freebsd.org (Postfix) with ESMTP id 48A1F13C467 for ; Thu, 27 Sep 2007 06:53:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1502347nzf for ; Wed, 26 Sep 2007 23:53:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=aJ0O/W7I1COQTRg/3INvl9D0+HUHlpaDs+JIXRPsumE=; b=iI9PjEKuwnyCm4iuEOcOajIfO9OQc8rPB2L64/86Eb3zoMA7WXhIZDavYLS3XNY7M5LDUz29iRSiiwiogEub+X3i5agsMqq44LI2qyAsP23uAIbNPvTmLRWPA5IH+Cbagq9O0n7N9o+RuupMQlQVWQyKEIJzpXjChFnVt/mkxCM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=mTdSGXREJMacKyj8hRjeMrr0ZTe4yiOUg4V9Kka6ff/eVi9NwDX2Peh7A3pyqC7Uvb8tW13JcR/ZCRJCGh9juVNKb/ifKWoOCKeJ3gKyIUaMgczUn0iMoghTTTDudOdgMxR4VTPCZQmu/Jb5MLZ0Dg1joZUzdV9IZB+L31pjVSs= Received: by 10.114.73.1 with SMTP id v1mr754497waa.1190876030559; Wed, 26 Sep 2007 23:53:50 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id m40sm2876528waf.2007.09.26.23.53.47 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 26 Sep 2007 23:53:49 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l8R6o9J0003991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2007 15:50:09 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l8R6o9sI003990; Thu, 27 Sep 2007 15:50:09 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 27 Sep 2007 15:50:08 +0900 From: Pyun YongHyeon To: Chris Message-ID: <20070927065008.GD3692@cdnetworks.co.kr> References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240917p2776136fn50eb2d5bbbaeebf2@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3aaaa3a0709240917p2776136fn50eb2d5bbbaeebf2@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Stable , freebsd-hardware@freebsd.org Subject: Re: nfe driver 6.2 stable 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: Thu, 27 Sep 2007 06:53:52 -0000 On Mon, Sep 24, 2007 at 05:17:40PM +0100, Chris wrote: > On 24/09/2007, Jeremy Chadwick wrote: > > On Mon, Sep 24, 2007 at 12:57:23AM +0100, Chris wrote: > > > nfe0: flags=8843 mtu 1500 > > > options=8 > > > inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.x > > > inet x.x.x.x netmask 0xffffffff broadcast x.x.x.x > > > ether x > > > media: Ethernet autoselect (1000baseTX ) > > > status: active > > > > > > 1 - is there a man page for nfe anywhere? > > > > Closest thing I can find would be the manpage from -CURRENT's nfe(4), > > which is supposedly the same code. > > > > http://www.freebsd.org/cgi/man.cgi?query=nfe&apropos=0&sektion=0&manpath=FreeBSD+7-current&format=html > > > > > 2 - does it support hardware checksum I remember reading it does but > > > from ifconfig output it appears to not be in use so if it does support > > > it how do I enable it? > > > > It does support it, but I don't know the circumstances surrounding when > > it gets enabled. That is to say, it's known that some versions of the > > chip (and/or associated PHY) have bugs, so possibly hardware checksum > > offloading is known to be broken on the system you're on. Taken from my > > 7-CURRENT box at home (Asus A8N-E, nForce 4-based): > > > > nfe0: flags=8843 metric 0 mtu 1500 > > options=10b > > ether 00:15:f2:17:30:e9 > > inet 192.168.1.51 netmask 0xffffff00 broadcast 192.168.1.255 > > media: Ethernet 1000baseTX > > status: active > > > > I do not explicitly specify rxcsum or txcsum in my rc.conf ifconfig > > line. > > > > > 3 - same with TOS? > > > > TOS (type-of-service) or TSO? If TSO, see above ifconfig. > > > > > 4 - how do I enable jumbo frames if it supports it? > > > > You should take a bit more itme to read the webpage you obtained the > > driver from. I see these on the page: > > > > 2007/01/06 Added jumbo frame support. [...] Fixed a bug to handle > > Tx/Rx checksum offload settings with ifconfig. > > 2006/08/11 Added support for jumbo frame capability. > > > > yongari@ (Pyun YongHyeon) should be able to provide additional help > > with both. > > > > > 5 - is it safe to use with zero copy sockets? > > > > No idea. > > > > > 6 - I currently have both net.isr.direct and mpsafenet disabled is > > > this driver safe to use on them? > > > > No idea. > > > > -- > > | Jeremy Chadwick jdc at parodius.com | > > | Parodius Networking http://www.parodius.com/ | > > | UNIX Systems Administrator Mountain View, CA, USA | > > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > > > > > Ok to recap I have nforce 430 MCP13 > > I checked the src and current and 6.2-stable driver I am using are the > same version number but my driver src has this added above tunables. > > /* definitions for backporting RELENG-6 */ > #ifndef IFCAP_TSO4 > #define IFCAP_TSO4 0 > #define CSUM_TSO 0 > #endif > #ifndef VLAN_CAPABILITIES > #define VLAN_CAPABILITIES(x) > #endif > #ifndef IFCAP_VLAN_HWCSUM > #define IFCAP_VLAN_HWCSUM 0 > #endif > > I am guessing If I set the values to 1 I get the features but would > like someone to confirm this for me before I try it thanks. I only > have remote access so if it stops the card working I lose access to > the box. > Do you have strong evidence that nForce 430(MCP13, aka MCP51) supports hardware checksum offload? AFAIK MCP13 does NOT have support checksum offload/jumbo frame as well as TSO. If you want to experiment checksum offload capability of MCP13 hardware replace the following line in nfe_attach(). From: case PCI_PRODUCT_NVIDIA_MCP51_LAN1: case PCI_PRODUCT_NVIDIA_MCP51_LAN2: sc->nfe_flags |= NFE_40BIT_ADDR | NFE_PWR_MGMT; break; To: case PCI_PRODUCT_NVIDIA_MCP51_LAN1: case PCI_PRODUCT_NVIDIA_MCP51_LAN2: sc->nfe_flags |= NFE_40BIT_ADDR | NFE_PWR_MGMT | NFE_HW_CSUM; ^^^^^^^^^^^^^^ break; -- Regards, Pyun YongHyeon