From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 15:45:38 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3736616A41A for ; Mon, 24 Sep 2007 15:45:38 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id C888C13C458 for ; Mon, 24 Sep 2007 15:45:37 +0000 (UTC) (envelope-from chrcoluk@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so956627ugf for ; Mon, 24 Sep 2007 08:45:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=N7Ht4prgjE+3rzs0ZuoZfQqd5sofkD2Ph5nSB1b/vWo=; b=MXvMH5RQcBbLvrqeoE3SUnvBliRci1hNaEhBJAiYaB6YFSD1KcOdlvLIHlc/rx32JocDF1qGtCjlvC5bIaPlGUOWoNgQ+38NdeUFkBKhs8TsuysWjYoCz+4CasOEeC2BUbCPdA9dztVxEHLUx0bFQ0NFNCMfuVlRpY81MRtyXKU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aArA2sacL4un8x9QQfgpkeDEpYboaAyuXeP+X6ip/kfMi+XM+AXYk9lsTKmSBQcDU0F9W5jcUXPx4g1A+BnNqqabIsTfylO4ThIHrHB49klSSLaAut2e4I6wgKEoHRUVyXHB98vhvigLE30CHj1+D+wMCr9tbOzA8KPZUG510xk= Received: by 10.66.221.5 with SMTP id t5mr4267778ugg.1190648736392; Mon, 24 Sep 2007 08:45:36 -0700 (PDT) Received: by 10.66.237.15 with HTTP; Mon, 24 Sep 2007 08:45:36 -0700 (PDT) Message-ID: <3aaaa3a0709240845q37e3b7c8g84239529b4136ce2@mail.gmail.com> Date: Mon, 24 Sep 2007 16:45:36 +0100 From: Chris To: Chris , freebsd-hardware@freebsd.org, "FreeBSD Stable" In-Reply-To: <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3aaaa3a0709231657r3264c873ife71800731608b03@mail.gmail.com> <20070924020116.GA36909@eos.sc1.parodius.com> <3aaaa3a0709240844j2603a050nd09bb5482a0f3c21@mail.gmail.com> Cc: Subject: Re: nfe driver 6.2 stable X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 15:45:38 -0000 On 24/09/2007, 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 | > > > > > > Thanks yes I meant TSO sorry, I would guess with the checksum either > the 6.x driver is older and not fully implemented yet, the 6.x driver > does need more patches for certian chipsets so would indicate its > older then the CURRENT driver. Or as you said my chipset is known to > be unstable with the hardware checksums. > > The card is more stable when using nve driver no crashes still but the > performance is around the same maxing out at around 200mbit. I was > expecting nearer 400-500mbit. > > e1000phy0: on miibus0 > > Is the line from dmesg, I believe in CURRENT mpsafe is always on > regardless so if you have no problems then its a good sign and I will > reenable mpsafe networking (default). > > Thanks really appreciated. > > Chris > Sorry I meant the card is more stable with this nfe then the nve driver. Chris