From owner-freebsd-stable Wed Jan 20 14:35:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27352 for freebsd-stable-outgoing; Wed, 20 Jan 1999 14:35:04 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from capsicum.wsrcc.com (c460058-a.frmt1.sfba.home.com [24.1.65.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27334 for ; Wed, 20 Jan 1999 14:35:01 -0800 (PST) (envelope-from wolfgang@wsrcc.com) Received: (from wolfgang@localhost) by capsicum.wsrcc.com (8.9.1a/8.9.1) id OAA02878; Wed, 20 Jan 1999 14:34:44 -0800 (PST) From: Wolfgang Rupprecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13990.23043.921555.147980@capsicum.wsrcc.com> Date: Wed, 20 Jan 1999 14:34:43 -0800 (PST) To: Gregory Bond Cc: Brian Del Vecchio , Chrisy Luke , freebsd-stable@FreeBSD.ORG Subject: Re: Cisco/Intel Ethernet Trunking In-Reply-To: <199901202228.JAA00466@lightning.itga.com.au> References: <199901202228.JAA00466@lightning.itga.com.au> X-Mailer: VM 6.63 under Emacs 19.34.1 Organization: W S Rupprecht Computer Consulting, Fremont CA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Bond writes: > > you may end up > > getting TCP > > segments received out of order. For some implementations of TCP, this will > > result > > in segments being discarded and retransmitted, a noticable and detrimental > > side effect. > > Any TCP implementation this poor deserves all the bad performance they get. > Out-of-order reassembly has been a requirement of TCP stacks since TCP was > invented. The problem is not really out-of-order reassembly, but out of order packets triggering the fast-retransmit logic. Basically the receiver sees the out of order packet and thinks a segment has been lost and it retransmits a duplicate ack for the last packet. The transmitter sees the dup ack, figures the next segment has been lost and retransmits that. -wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message