Re: [PATCH] tcp: add setsockopt to disable slow start after idle

[Andi Kleen <andi@firstfloor.org>]

David Miller <davem@davemloft.net> writes:
>
> It is a very dangerous option to enable, and depends deeply
> upon the characteristics of your network and the paths by
> which remote hosts are reached.
>
> Therefore, only the system administrator can determine whether it is
> safe to enable this, and that's why it can only be changed via sysctl.
> Lettting arbitrary applications change this aspect of TCP is beyond
> dangerous.
>
> I will not be applying this patch.

It should be safe as long as you don't have any packet loss (which
means the network can take it). Or I am missing something?

So perhaps allow it, but force disable it on the first retransmit?

There could be still some over subscription in the first window,
but hopefully not too bad.

Ok it could be still gamed by opening lots of sockets, but that
problem is there anyways.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.