Date: Mon, 02 Oct 2000 07:33:06 -0700 From: "Kevin Oberman" <oberman@es.net> To: Jonathan Lemon <jlemon@flugsvamp.com> Cc: julian@elischer.org, net@FreeBSD.ORG Subject: Re: SACK in FreeBSD TCP. Message-ID: <200010021433.e92EX6r15583@ptavv.es.net> In-Reply-To: Your message of "Mon, 02 Oct 2000 08:58:37 CDT." <200010021358.e92DwbA14157@prism.flugsvamp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I can't comment on what the symptoms are in Oz, but testing on very large streams done last year by ESnet, Lawrence Berkeley National Laboratory, and Argonne National Laboratory made it painfully obvious that trying to run a single TCP stream of over 200 Mbps between Chicago and California was impossible without SACK. It does require many other things, like very large windows and fast recovery, but without SACK it's hopeless. In our testing we used Solaris and Tru64 UNIX, but FreeBSD was not an option because of the lack of SACK. As a strong proponent of FreeBSD and the FreeBSD network stack in particular, this was a bit painful to me. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010021433.e92EX6r15583>