From owner-freebsd-net Mon Feb 26 13:46: 7 2001 Delivered-To: freebsd-net@freebsd.org Received: from alpo.whistle.com (s206m1.whistle.com [207.76.206.1]) by hub.freebsd.org (Postfix) with ESMTP id 20A2537B491 for ; Mon, 26 Feb 2001 13:46:03 -0800 (PST) (envelope-from mark@whistle.com) Received: from [10.1.10.113] (PBG3.whistle.com [207.76.207.169]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA11201; Mon, 26 Feb 2001 13:42:46 -0800 (PST) Mime-Version: 1.0 X-Sender: mark@207.76.206.1 Message-Id: In-Reply-To: <20010225085626.V5714@prism.flugsvamp.com> References: <20010224142742.T5714@prism.flugsvamp.com> <20010225085626.V5714@prism.flugsvamp.com> Date: Mon, 26 Feb 2001 13:39:37 -0800 To: Jonathan Lemon , Paul Herman From: Mark Peek Subject: Re: I have delayed ACK problems Cc: Jonathan Lemon , Garrett Wollman , net@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 8:56 AM -0600 2/25/01, Jonathan Lemon wrote: >On Sun, Feb 25, 2001 at 11:10:54AM +0100, Paul Herman wrote: >> 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. > >Hmm, yes, by doing that, I'm able to reproduce the condition locally, >thanks for pointing out a good test case. Thanks for the update. Jonathan, does it make sense to commit the current patch since it solves Paul's problem (and presumably doesn't break existing networking) or should it wait until the "tar cf host:" problem can be solved? I'm basically neutral on which way to go but it sounded like a big network performance issue for Paul when he initially reported the bug. (It might be affecting more people but they probably haven't done the analysis to better understand the problem.) Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message