lkml.org 
[lkml]   [2002]   [Dec]   [13]   [last100]   RSS-feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
Complete thread (EXPERIMENTAL)
/
DateFri, 13 Dec 2002 12:46:15 +0100 (CET)
FromBogdan Costescu <>
SubjectRe: R: Kernel bug handling TCP_RTO_MAX?
Digg This
On Thu, 12 Dec 2002, David S. Miller wrote:

This is well understood, the problem is that BSD's coarse timers are going to cause all sorts of problems when a Linux stack with a reduced MIN RTO talks to it.

Sorry to jump into the discussion without a good understanding of inner workings of TCP, I just want to share my view as a possible user of this: one of the messages at the beginning of the thread said that this would be useful on a closed network and I think that this point was overlooked.
Think of a closed network with only Linux machines on it (world domination, right :-)) like a Beowulf cluster, web frontends talking to NFS fileservers, web frontends talking to database backends, etc. Again as proposed earlier, border hosts (those connected to both the closed network and outside one) could change their communication parameters based on device or route and this would become an internal affair that would not affect communication with other stacks.

I don't want to suggest to make this the default behaviour; rather, have it a parameter that can be changed by the sysadmin and have the current value as default.

-- 
Bogdan Costescu

IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu@IWR.Uni-Heidelberg.De

\
ISP Services
Valid XHTML 1.0!\ /
Valid CSS! Last update: 2005-03-22 12:31    [W:0.323 / U:0.070 seconds]
©2003-2005 Jasper Spaans