[lkml]   [2010]   [Apr]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] tcp: add setsockopt to disable slow start after idle
On 11/04/2010 00:47, David Miller wrote:
> From: Cristian KLEIN<>
> Date: Sat, 10 Apr 2010 14:09:03 +0200
>> Could you please explain me why it is dangerous? To me it seems that
>> it's just like allowing applications to disable NAGLE or to choose a
>> congestion control algorithm.
> Because you can cause undue congestion to other people on the network
> because you are believing path information that has been outdated and
> has not been validated by sending data for a certain amount of time.

I consider your argument an important concern, but I'm not quite
convinced this patch is so bad.

An application which does not need this behaviour will continue to slow
start after idle by default.

Without this patch, an application which needs this behaviour (i.e. not
to slow start after idle) is forced to implement its own UDP-based
protocol with all the congestion control, retransmission etc. Undue
congestion might still occur.

If you don't agree with the above two points, would you consider
accepting a patch with an allow_user_fast_start_after_idle sysctl?


 \ /
  Last update: 2010-04-11 20:47    [W:0.054 / U:1.572 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site