Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 27 Feb 2002 12:09:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 27 Feb 2002 12:08:58 -0500 Received: from pizda.ninka.net ([216.101.162.242]:21125 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Wed, 27 Feb 2002 12:08:47 -0500 Date: Wed, 27 Feb 2002 09:06:27 -0800 (PST) Message-Id: <20020227.090627.109057645.davem@redhat.com> To: nivedita@us.ibm.com Cc: bjorn.wesen@axis.com, linux-kernel@vger.kernel.org Subject: Re: What is TCPRenoRecoveryFail ? From: "David S. Miller" In-Reply-To: In-Reply-To: X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org From: "Nivedita Singhvi" Date: Wed, 27 Feb 2002 09:03:27 -0800 Windows and Linux dont agree on DSACK options in some situations, leading to symptoms you describe sometimes.. There are no options to negotiate DSACK, SACK implies DSACK will cause no harm. An pre-DSACK implementation of SACK should effectively treat the DSACKs as nops, ie. they are harmless. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/