From owner-freebsd-current@FreeBSD.ORG Fri Nov 6 20:31:52 2009 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 6D38B106568F for ; Fri, 6 Nov 2009 20:31:52 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f202.google.com (mail-pz0-f202.google.com [209.85.222.202]) by mx1.freebsd.org (Postfix) with ESMTP id 349478FC1E for ; Fri, 6 Nov 2009 20:31:52 +0000 (UTC) Received: by pzk40 with SMTP id 40so903142pzk.7 for ; Fri, 06 Nov 2009 12:31:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=cw+YdmMP+I79bF6j7qd4VGQ8Mu7Mtg/HnE7N74J6KRs=; b=h726e7ulArq2kW+H2BsrQ/xn5BgbqMbU5jrxomEJxU5OOlN74WPCGjEvhXalTjf5TW Isp0V8Wkev2BsitM0nYhXUuuRBbDaTiHCeXtxrn6MfWMb3gt4hJHoEPsS3fz/wNtxeHA 7phD2G/3N1Ho7It4tk3Pbphjj++1qAGk5nZ4o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=sRyBm6eSiixKajXuIqmUxGnNG6hPN9aq3SKTEoktRdVaQBRgXDKFz2TFS+gAO6S5lN D7FaSGK2S3PW7tw53ErK643J6qJ+NFxIuMZfvbHeJbGjXeomDe9zeNIl69cPY+pGQWo1 KmjornOFV7yRNwFv4ax2tYy8yEypilIbneCqU= Received: by 10.115.151.8 with SMTP id d8mr7134307wao.180.1257539511319; Fri, 06 Nov 2009 12:31:51 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 23sm208121pxi.9.2009.11.06.12.31.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 06 Nov 2009 12:31:50 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 6 Nov 2009 12:31:16 -0800 From: Pyun YongHyeon Date: Fri, 6 Nov 2009 12:31:16 -0800 To: Rick Macklem Message-ID: <20091106203116.GZ1256@michelle.cdnetworks.com> References: <4AF0B7DF.9030405@freebsd.org> <030A8229-9707-4F70-B4BE-584F1BF9ECEC@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, Rui Paulo Subject: Re: Help needed: TCP Wizards (was 8.0-RC1 NFS client timeout issue) 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: Fri, 06 Nov 2009 20:31:52 -0000 On Fri, Nov 06, 2009 at 03:30:39PM -0500, Rick Macklem wrote: > > > On Thu, 5 Nov 2009, Rui Paulo wrote: > > > > >Are you running TSO? > > > Wow, I owe you a beer:-) That was the magic bullet... > > I'm a dinosaur, so when I first saw this, I thought of that wonderful > time sharing front end to IBM mainframes I had the priviledge of using > in the 70s. (There was also a TSO emulator in the early Unix releases, > which set your terminal to the worst possible setting imaginable and > introduced delays of seconds when you tried to do anything. It was > pretty funny for those of us who had experienced the real thing.) > > Anyhow, I figured you probably didn't mean this so I grep'd around > and found net.inet.tcp.tso, set it to 0 and...the problem went away. > (I have gotten a RST for the new port# once since then, but it was > in the middle of the 3way handshake instead of after it, so it didn't > cause any grief, just another 3way handshake right away.) > > I have no idea if the problem is something generic w.r.t. TSO or specific > to the Intel 82801BA/CAM and/or the fxp driver for it. (I checked and none fxp(4) has TSO support but I don't think 82801BA has TSO capability. Only i82550 and i82551 support TSO. You can check it with ifconfig if fxp(4) think the controller supports TSO. > of the other net cards I have lying around have TSO support, so I can't > test this by replacing the net card/driver.) > > Does anyone know enough about TSO to know if the problem is net chip > specific of generic to using it? > > Thanks for the help. I don't think I would have ever found that, rick >