Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S267476AbSLLU2w>; Thu, 12 Dec 2002 15:28:52 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S267470AbSLLU2w>; Thu, 12 Dec 2002 15:28:52 -0500
Received: from pizda.ninka.net ([216.101.162.242]:6826 "EHLO pizda.ninka.net")
	by vger.kernel.org with ESMTP id <S267467AbSLLU2v>;
	Thu, 12 Dec 2002 15:28:51 -0500
Date: Thu, 12 Dec 2002 12:32:32 -0800 (PST)
Message-Id: <20021212.123232.32776934.davem@redhat.com>
To: stefano.andreani.ap@h3g.it
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: R: Kernel bug handling TCP_RTO_MAX?
From: "David S. Miller" <davem@redhat.com>
In-Reply-To: <047ACC5B9A00D741927A4A32E7D01B73D66178@RMEXC01.h3g.it>
References: <047ACC5B9A00D741927A4A32E7D01B73D66178@RMEXC01.h3g.it>
X-FalunGong: Information control.
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
Content-Length: 679
Lines: 16

   From: "Andreani Stefano" <stefano.andreani.ap@h3g.it>
   Date: Thu, 12 Dec 2002 21:18:21 +0100

   Never say never ;-) 
   I need to change it now as a temporary workaround for a problem in
   the UMTS core network of my company. But I think there could be
   thousands of situations where a fine tuning of this TCP parameter
   could be useful.

You still aren't giving specific examples and details of
the problem you are seeing.
-
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/