From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hagen Paul Pfeifer Subject: Re: [net-next PATCH v4 1/3] net: TCP thin-stream detection Date: Mon, 22 Feb 2010 17:06:25 +0100 Message-ID: <228e2e29ccd24144a77d42cfc5bc72fa@localhost> References: <20100221102102.GB1311@ucw.cz> <2EC47E8B-BC4C-4DAB-86ED-F702D67F8AD0@nokia.com> <20100221.150311.193707249.davem@davemloft.net> <87k4u5mh9u.fsf@basil.nowhere.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: Lars Eggert , David Miller , , , , , , , , , , , , To: Andi Kleen Return-path: In-Reply-To: <87k4u5mh9u.fsf@basil.nowhere.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Mon, 22 Feb 2010 16:17:33 +0100, Andi Kleen wrote: > Lars Eggert writes: > >> If it's off by default there is no issue. > > Still a sufficient large number of people might turn it on > and then the network would melt. Then we should apply the same policy as used for the congestion control algorithms!? Restrict the usage to change the standard behavior via Kconfig (e.g. menuconfig TCP_CONG_ADVANCED) or even more restricted demand for CAP_NET_ADMIN. Hagen