From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: rhee@eos.ncsu.edu, netdev@vger.kernel.org
Subject: Re: [PATCH] tcp: mark BIC as experimental
Date: Fri, 31 Oct 2008 09:41:13 -0700 [thread overview]
Message-ID: <20081031094113.2bab9140@extreme> (raw)
In-Reply-To: <20081031.005033.172610018.davem@davemloft.net>
On Fri, 31 Oct 2008 00:50:33 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Stephen Hemminger <shemminger@vyatta.com>
> Date: Thu, 30 Oct 2008 08:36:41 -0700
>
> > Change the configuration defaults to mark BIC as experimental.
> > BIC is too aggressive and was replaced by CUBIC. Debian was picking
> > BIC in their default config (should be fixed by now), but the configuration
> > documentation did not make it explicit that this was a bad idea.
> >
> > Also update the URLs in the configuration documentation to current
> > locations.
> >
> > Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
>
> I understand your intention, but I'm not so sure we should do this.
>
> It's more than a double standard to make this change, yet still
> allow things like HTCP to still be a default.
>
> And you can't even make this selection without asking for
> TCP_CONG_ADVANCED. Well... duh!
Some architectures were setting TCP_CONG_ADVANCED and choosing BIC
arch/arm/configs/at91rm9200dk_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/at91rm9200ek_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/ateb9200_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/collie_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/kafa_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/kb9202_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/ks8695_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/lpd7a404_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/netx_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/pnx4008_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/realview_defconfig:CONFIG_TCP_CONG_BIC=y
arch/arm/configs/versatile_defconfig:CONFIG_TCP_CONG_BIC=y
arch/ia64/configs/bigsur_defconfig:CONFIG_TCP_CONG_BIC=y
arch/ia64/configs/gensparse_defconfig:CONFIG_TCP_CONG_BIC=y
arch/ia64/configs/sim_defconfig:CONFIG_TCP_CONG_BIC=y
arch/mips/configs/bcm47xx_defconfig:CONFIG_TCP_CONG_BIC=y
arch/mips/configs/rb532_defconfig:CONFIG_TCP_CONG_BIC=m
arch/mips/configs/tb0287_defconfig:CONFIG_TCP_CONG_BIC=y
arch/powerpc/configs/ppc6xx_defconfig:CONFIG_TCP_CONG_BIC=m
next prev parent reply other threads:[~2008-10-31 16:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 21:28 [PATCH] CUBIC v2.3 with new improved slow start Injong Rhee
2008-10-29 22:39 ` Stephen Hemminger
2008-10-29 23:14 ` Injong Rhee
2008-10-29 23:40 ` Stephen Hemminger
2008-10-29 23:53 ` Rick Jones
2008-10-30 0:54 ` Injong Rhee
2008-10-30 1:08 ` Rick Jones
2008-10-29 23:45 ` David Miller
2008-10-30 15:36 ` [PATCH] tcp: mark BIC as experimental Stephen Hemminger
2008-10-31 7:50 ` David Miller
2008-10-31 16:41 ` Stephen Hemminger [this message]
2008-10-31 19:04 ` David Miller
2008-10-31 19:16 ` [RFC] tcp: make H-TCP the default congestion control Stephen Hemminger
2008-10-31 19:43 ` Sangtae Ha
2008-10-31 20:02 ` rhee
2008-11-02 4:29 ` David Miller
2008-11-02 7:27 ` [PATCH] CUBIC v2.3 with new improved slow start David Miller
2008-11-03 22:19 ` Sangtae Ha
2008-11-03 22:49 ` Stephen Hemminger
2008-11-04 1:12 ` 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=20081031094113.2bab9140@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rhee@eos.ncsu.edu \
/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).