From owner-freebsd-net Wed Jan 24 13:57:41 2001 Delivered-To: freebsd-net@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1285537B400 for ; Wed, 24 Jan 2001 13:57:23 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id IAA26102; Thu, 25 Jan 2001 08:57:02 +1100 Date: Thu, 25 Jan 2001 08:56:54 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Jordan Hubbard Cc: Paul Herman , Jonathan Lemon , net@FreeBSD.ORG Subject: Re: I have delayed ACK problems In-Reply-To: <77394.980367750@winston.osd.bsdi.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 Wed, 24 Jan 2001, Jordan Hubbard wrote: > > Something just doesn't sit well me. This shouldn't happen in a > > 100Mbit LAN. This seems like a plain vanilla network transaction, and > > FreeBSD is failing on something, where other OSes in the same > > environment don't. > > You're almost certainly correct that there's a misfeature lurking in > there somewhere, I don't think anybody's arguing that particular > point, it's just that you're also (sadly) in a much better position to > diagnose this than [m]any of your readers since we don't have an > active failure scenario to analyze like you do. :( I diagnosed similar problems in rmt(8) a few (?) months ago. Try: tar cf localhost:/tmp/foo /boot/kernel With the FreeBSD defaults, this crawls at almost precisely 100K/sec due to its protocol waiting for an ack after every 10K block and acks being delayed by 100 msec. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message