Date: Wed, 20 Jan 1999 14:34:43 -0800 (PST) From: Wolfgang Rupprecht <wolfgang@wsrcc.com> To: Gregory Bond <gnb@itga.com.au> Cc: Brian Del Vecchio <bdv@parlez.com>, Chrisy Luke <chrisy@flix.net>, freebsd-stable@FreeBSD.ORG Subject: Re: Cisco/Intel Ethernet Trunking Message-ID: <13990.23043.921555.147980@capsicum.wsrcc.com> In-Reply-To: <199901202228.JAA00466@lightning.itga.com.au> References: <199901202228.JAA00466@lightning.itga.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13990.23043.921555.147980>