Date: Wed, 16 Jul 2008 09:27:33 +0200 From: Dimitry Andric <dimitry@andric.com> To: pyunyh@gmail.com Cc: freebsd-current@FreeBSD.org Subject: Re: Call for testers: re(4) and RTL8168C/RTL8168CP/RTL8111C/RTL8111CP Message-ID: <487DA2E5.3080201@andric.com> In-Reply-To: <20080714013519.GE36245@cdnetworks.co.kr> References: <484BC9FB.2040605@andric.com> <20080609012657.GD12521@cdnetworks.co.kr> <484D215A.7050700@andric.com> <20080609123206.GF12521@cdnetworks.co.kr> <484D25CC.9050106@andric.com> <20080610050550.GB17874@cdnetworks.co.kr> <484E9377.2050609@andric.com> <20080611005814.GA3529@cdnetworks.co.kr> <48666CD7.9020706@andric.com> <20080630043156.GB79537@cdnetworks.co.kr> <20080714013519.GE36245@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2008-07-14 03:35, Pyun YongHyeon wrote:
> Here is patch for re(4) link handling.
> Copy if_re.c and if_rlreg.h from HEAD to RELENG_7 and apply
> attached one. If you still see watchdog timeouts, please turn off
> TSO and let me know how it goes.
I've tested this trough several reboots, and I haven't been bitten by
any watchdogs yet. :) I'll run some stress tests today, to see if it
handles that too.
> One user reported TSO issues on 8169 family controllers but I
> can't reproduce this on my 8169 hardware so it could be related
> with silicon bug of sepecific revision of the hardware.
I'm using re's default settings, which seem to be:
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
So TSO for IPv4 but not IPv6, right? I haven't yet seen any problems
because of it. What would be a good way to "exercise" TSO?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?487DA2E5.3080201>