Vlad Yasevich wrote:
> 
> Florian Niederbacher wrote:
>> Hi,
>> thank you very much for the patch. Now it works like a charm! I need now
>> only to change
>> the MAX_BURST value otherwise after the connection goes into idle state
>> the cwnd will be reduced to fast.
>> (Default MAX_BURST  = 4 and MTU = 1500 ->  cwnd = 6000)
>> I guess this is intended by the rule from RFC 4960 in section
>>
>>
>>      6.1. Transmission of DATA Chunks
>>
>>
>>      D) When the time comes for the sender to transmit new DATA chunks,
>>      the protocol parameter Max.Burst SHOULD be used to limit the
>>      number of packets sent.  The limit MAY be applied by adjusting
>>      cwnd as follows:
>>
>>      if((flightsize + Max.Burst*MTU) < cwnd) cwnd = flightsize +
>>      Max.Burst*MTU
>>
>>
>> I am right?
>>
> 
> I think this rule gets mis-applied in this situation.  The idea behind max burst
> is to not burst out a lot of data in response to a SACK.
> 
> Can you try this patch and let me know what you see.

And now actually with a patch... :)