netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Horms <horms@debian.org>
To: "Benoît Dejean" <benoit@placenet.org>, 337089@bugs.debian.org
Cc: NetDev <netdev@vger.kernel.org>
Subject: Bug#337089: linux-image-2.6.14-1-powerpc: add CONFIG_TCP_CONG_BIC=y
Date: Fri, 4 Nov 2005 12:27:27 +0900	[thread overview]
Message-ID: <20051104032726.GD4708@verge.net.au> (raw)
In-Reply-To: <20051102162451.0002CF64E@ibook.free.fr>

On Wed, Nov 02, 2005 at 05:24:50PM +0100, Benoît Dejean wrote:
> Package: linux-image-2.6.14-1-powerpc
> Version: 2.6.14-1
> Severity: normal
> 
> Hi,
> Linux < 2.6.14 used to have every TCP congestion algorithms as builtins but
> NewReno + BIC was default.
> 
> Linux 2.6.14 has splitted these features into modules. But default remains
> NewReno + BIC accordint to CONFIG_TCP_CONG_ADVANCED help message :
> 
> "Nearly all users can safely say no here, and a safe default selection will
> be made (BIC-TCP with new Reno as a fallback)."
> 
> And indeed NewReno+BIC is a good and safe default. Much better than NewReno
> 
> But Debian .config has CONFIG_TCP_CONG_BIC=m (CONFIG_TCP_CONG_*=m) which
> makes NewReno default. So this is like a "regression". I'd like debian kernel
> to have CONFIG_TCP_CONG_BIC=y provided that one can easily switch to another
> algorithm (using /proc/sys/net/ipv4/tcp_congestion_control).

Hi Netdev,

could someone please comment on what a good default congestion
algorithm setup for distribution kernels is?

Thanks

-- 
Horms

       reply	other threads:[~2005-11-04  3:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051102162451.0002CF64E@ibook.free.fr>
2005-11-04  3:27 ` Horms [this message]
2005-11-04 18:24   ` Bug#337089: linux-image-2.6.14-1-powerpc: add CONFIG_TCP_CONG_BIC=y Ian McDonald
2005-11-07  6:36     ` Horms

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=20051104032726.GD4708@verge.net.au \
    --to=horms@debian.org \
    --cc=337089@bugs.debian.org \
    --cc=benoit@placenet.org \
    --cc=netdev@vger.kernel.org \
    /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).