From owner-freebsd-current@FreeBSD.ORG Thu Jul 17 01:44:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7828E1065672 for ; Thu, 17 Jul 2008 01:44:27 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by mx1.freebsd.org (Postfix) with ESMTP id 008D98FC26 for ; Thu, 17 Jul 2008 01:44:26 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so7136831rvf.43 for ; Wed, 16 Jul 2008 18:44:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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=NL2dp6QGJu5AtLXiWatM9c3DuDMwIwvhbCNs/NC0gck=; b=SvPHjWcKuW9ebFfGMGjrEJirUatMvUZHuOgAjcxNabvkm4+sBZec7lXWpvqV7FIlkx oj2blWuZInxeU6t8lawzTlVNfzuLLje8f1nTXfLUUSH/+v4H1NmNtcuR7iaTiIV6ZntD +KUz7dSNkTd9UIjfp+3XlqCovGAevSRU1SbgA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=RPTZak83MPbFKNfVXMw7Mo5sqjXkAvBCqYYBpoG2iU4qelyr68mySRwd+s65NEKGB1 xfGUI2jSWIQOTnaaC/penciAYCquaauMhMYuFuKpSglG/5M53DKRdrwuxGsfB5Pi+Ta0 ZsXHYpQ9RS38j6iNIFGm5W69GPxqvhJkyNF2g= Received: by 10.140.202.12 with SMTP id z12mr806496rvf.186.1216259066827; Wed, 16 Jul 2008 18:44:26 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id f21sm15077889rvb.0.2008.07.16.18.44.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 16 Jul 2008 18:44:25 -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 m6H1gFxU049139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Jul 2008 10:42:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m6H1gEmb049138; Thu, 17 Jul 2008 10:42:14 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 17 Jul 2008 10:42:14 +0900 From: Pyun YongHyeon To: Dimitry Andric Message-ID: <20080717014214.GB48743@cdnetworks.co.kr> References: <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> <487DA2E5.3080201@andric.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <487DA2E5.3080201@andric.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@FreeBSD.org Subject: Re: Call for testers: re(4) and RTL8168C/RTL8168CP/RTL8111C/RTL8111CP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2008 01:44:27 -0000 On Wed, Jul 16, 2008 at 09:27:33AM +0200, Dimitry Andric wrote: > 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 metric 0 mtu 1500 > options=399b > > So TSO for IPv4 but not IPv6, right? I haven't yet seen any problems Yes. > because of it. What would be a good way to "exercise" TSO? One developer reported TSO breakage on 8169 controller but I couldn't reproduce it on my hardware. It seems that the TSO breakage also resulted in watchdog timeouts for his case. Just plain bulk-transfers of large files(ftp, scp etc) will automatically take advantage of TSO feature. You can easily check them with tcpdump on Tx side as TCP segment size is larger than interface MTU. -- Regards, Pyun YongHyeon