From owner-freebsd-net Sun Feb 25 2:11:42 2001 Delivered-To: freebsd-net@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id 55DF237B491 for ; Sun, 25 Feb 2001 02:11:40 -0800 (PST) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-72-230.netcologne.de [213.168.72.230]) by mr200.netcologne.de (Mirapoint) with ESMTP id ABT33922; Sun, 25 Feb 2001 11:11:36 +0100 (CET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.2/8.11.2) with ESMTP id f1PAAsQ65112; Sun, 25 Feb 2001 11:10:54 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Sun, 25 Feb 2001 11:10:54 +0100 (CET) From: Paul Herman To: Jonathan Lemon Cc: Mark Peek , Garrett Wollman , Subject: Re: I have delayed ACK problems In-Reply-To: <20010224142742.T5714@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 24 Feb 2001, Jonathan Lemon wrote: > On Sat, Feb 24, 2001 at 11:19:02AM -0800, Mark Peek wrote: > > Was there ever a final resolution to this problem? > > The patches are still sitting in my tree, as I've been unable > to come up with a test case that actually makes a difference. > > The "tar cf host:..." example is bogus, as the problem here is Jonathan is right, the patch doesn't solve the general "tar cf host:" problem, but it was similar enough to what we were seeing in production -- changing the MTU on lo0 to 1500 will make the "tar cf host:" problem/solution more apparent, when host == localhost. In anycase, we are very happy with the patch on our production servers, as it really did solve our problem. I believe the patch is 100% correct, it just doesn't fix 100% of the delayed ACK problems. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message