From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: Lars Eggert <lars.eggert@nokia.com>,
David Miller <davem@davemloft.net>,
<zimmermann@nets.rwth-aachen.de>, <pavel@ucw.cz>,
<apetlund@simula.no>, <netdev@vger.kernel.org>,
<ilpo.jarvinen@helsinki.fi>, <eric.dumazet@gmail.com>,
<Arnd.Hannemann@nets.rwth-aachen.de>,
<linux-kernel@vger.kernel.org>, <shemminger@vyatta.com>,
<william.allen.simpson@gmail.com>, <damian@tvk.rwth-aachen.de>,
<ebiederm@xmission.com>
Subject: Re: [net-next PATCH v4 1/3] net: TCP thin-stream detection
Date: Mon, 22 Feb 2010 17:06:25 +0100 [thread overview]
Message-ID: <228e2e29ccd24144a77d42cfc5bc72fa@localhost> (raw)
In-Reply-To: <87k4u5mh9u.fsf@basil.nowhere.org>
On Mon, 22 Feb 2010 16:17:33 +0100, Andi Kleen <andi@firstfloor.org> wrote:
> Lars Eggert <lars.eggert@nokia.com> 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
next prev parent reply other threads:[~2010-02-22 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 14:40 [net-next PATCH v4 1/3] net: TCP thin-stream detection Andreas Petlund
2010-02-18 0:32 ` David Miller
2010-02-21 10:21 ` Pavel Machek
2010-02-21 11:23 ` Alexander Zimmermann
[not found] ` <2EC47E8B-BC4C-4DAB-86ED-F702D67F8AD0@nokia.com>
[not found] ` <20100221.150311.193707249.davem@davemloft.net>
2010-02-22 6:41 ` Lars Eggert
2010-02-22 15:17 ` Andi Kleen
2010-02-22 15:35 ` Alexander Zimmermann
2010-02-22 15:40 ` Andreas Petlund
2010-02-22 15:51 ` Andreas Petlund
2010-02-22 16:06 ` Hagen Paul Pfeifer [this message]
2010-02-22 22:13 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=228e2e29ccd24144a77d42cfc5bc72fa@localhost \
--to=hagen@jauu.net \
--cc=Arnd.Hannemann@nets.rwth-aachen.de \
--cc=andi@firstfloor.org \
--cc=apetlund@simula.no \
--cc=damian@tvk.rwth-aachen.de \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=lars.eggert@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=shemminger@vyatta.com \
--cc=william.allen.simpson@gmail.com \
--cc=zimmermann@nets.rwth-aachen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).