From owner-freebsd-net@FreeBSD.ORG Wed Mar 9 11:28:49 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3841A16A4DC for ; Wed, 9 Mar 2005 11:28:48 +0000 (GMT) Received: from mail.astra-sw.com (mail.astra-sw.com [82.140.87.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AF4343D5C for ; Wed, 9 Mar 2005 11:28:46 +0000 (GMT) (envelope-from Nickolay.Kritsky@astra-sw.com) Received: from exchange.stardevelopers4msi.com ([192.168.64.10]) by mail.astra-sw.com (8.12.11/8.12.11) with ESMTP id j29BSjq2064673 for ; Wed, 9 Mar 2005 14:28:45 +0300 (MSK) Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 9 Mar 2005 14:31:53 +0300 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD 4.x and OS-X tcp performance thread-index: AcUj3WThpsdkfv+sS3CssCF2BIUUXgArSWJg From: "Nickolay Kritsky" To: "Daniel Hartmeier" , "Charles Sprickman" cc: freebsd-net@freebsd.org Subject: RE: FreeBSD 4.x and OS-X tcp performance X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 11:28:50 -0000 Here is my $0.02 I have seen such a problem with TCP flows between FreeBSD 4.5 and SUN = servers. The same scenario - ACKs getting lost on the one side of the link, which = was clearly seen on the tcpdumps taken on each sides at one time. I am = not so good in theory, but as quick fix - setting Sun's NIC to HD = helped. My guess was that packets are lost in the switch queues because of "too = high" speed of Sun's NIC. Like overflowing some internal buffers. I = don't know if it's true. Nick -----Original Message----- From: Daniel Hartmeier [mailto:daniel@benzedrine.cx] Sent: Tuesday, March 08, 2005 3:47 PM To: Charles Sprickman Cc: freebsd-net@freebsd.org Subject: Re: FreeBSD 4.x and OS-X tcp performance According to RFC 793 (the original TCP specification), the client may (even should) wait at least one second before retransmitting any segment. However, RFC 2001 describes Fast Retransmission, where the third acknowledgment for the same segment should be interpreted as an indication of packet loss, and cause an immediate retransmission (without waiting for the timeout of at least one second). I'd have expected Mac OS X to both implement this and enable it by default, but maybe I'm wrong. There's a sysctl net.inet.tcp.newreno which defaults to 0, and which seems to affect things. If you google, you find patches like http://www.opendarwin.org/~fkr/xnu/mach_kernel-to-517.7.21-SACK.diff which doesn't just contain SACK code, but possibly fixes fast retransmissions when newreno is not set. I'm not sure if disabling the newreno sysctl should disable fast retransmissions, or whether that's a bug. So, the Mac OS X client is not wrong in honouring RFC 793 alone. It just suffers badly from any packet loss. For you, the more relevant question is why there's 1.2% packet loss between the Mac OS X client and FreeBSD server, even when connected directly with crossover. Daniel _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"