netdev
[Top] [All Lists]

Re: internal drops with tcp, kernel 2.2.16

To: mukesh agrawal <mukesh@xxxxxxxxxx>
Subject: Re: internal drops with tcp, kernel 2.2.16
From: Andi Kleen <ak@xxxxxx>
Date: Thu, 18 Jan 2001 12:51:32 +0100
Cc: netdev@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.10.10101171931200.5704-100000@SLASH.REM.CMU.EDU>; from mukesh@cs.cmu.edu on Thu, Jan 18, 2001 at 01:35:33AM +0100
References: <Pine.LNX.4.10.10101171931200.5704-100000@SLASH.REM.CMU.EDU>
Sender: owner-netdev@xxxxxxxxxxx
On Thu, Jan 18, 2001 at 01:35:33AM +0100, mukesh agrawal wrote:
> 2. If this can happen, is it worth changing? In particular, we might not
> want to wait the entire RTT before retransmitting the packet if it was
> dropped inside the kernel.

2.4 has most of the infrastructure neededfor that: TCP gets an error code now
when the device queue overflows. It currently doesn't send more aggressively
when this happens, but just doesn't advance snd_nxt, making established behave 
a bit better. 

I guess you could experiment with more aggressive reactions, especially 
for initial SYNs (no handling of this case there currently) 

The common problem of the dynamic IP changing is already mostly but not 
completelycovered by the ip_dynaddr socket address rewrite hack.  The main 
problem left in there is in the user space resolver library btw with its too 
short timeout.  

-Andi

-- 
This is like TV. I don't like TV.

<Prev in Thread] Current Thread [Next in Thread>