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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 11 Apr 2010 14:41:33 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	andi@...stfloor.org
Cc:	cristiklein@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tcp: add setsockopt to disable slow start after idle

From: Andi Kleen <andi@...stfloor.org>
Date: Sun, 11 Apr 2010 22:48:19 +0200

> 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?

Unless you can detect packet loss or queueing delay incurred by
everyone else on the internet, this won't work.

Look, just drop this discussion, people simply don't understand the
implications of what they are suggesting.

The only thing I am willing to consider is a per-route attribute for
this setting, because that would be another legitimate to make this
setting.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/