From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: TCP and reordering Date: Tue, 27 Nov 2012 21:06:11 -0500 (EST) Message-ID: <20121127.210611.1127622873924794001.davem@davemloft.net> References: <50B4F2DA.8020206@hp.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: rick.jones2@hp.com, netdev@vger.kernel.org To: saku@ytti.fi Return-path: Received: from shards.monkeyblade.net ([149.20.54.216]:43291 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750961Ab2K1CGQ (ORCPT ); Tue, 27 Nov 2012 21:06:16 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: Saku Ytti Date: Tue, 27 Nov 2012 19:15:20 +0200 > TCP used to be friendly to reordering before fast retransmit > optimization was implemented. You're talking about 20 years ago, because that's when fast retrasnmit was created. It's not like this got added recently. And the gains of fast retransmit far outweigh whatever strange justification would give for reordering packets on purpose.