* Bug#337089: linux-image-2.6.14-1-powerpc: add CONFIG_TCP_CONG_BIC=y
[not found] <20051102162451.0002CF64E@ibook.free.fr>
@ 2005-11-04 3:27 ` Horms
2005-11-04 18:24 ` Ian McDonald
0 siblings, 1 reply; 3+ messages in thread
From: Horms @ 2005-11-04 3:27 UTC (permalink / raw)
To: Benoît Dejean, 337089; +Cc: NetDev
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Bug#337089: linux-image-2.6.14-1-powerpc: add CONFIG_TCP_CONG_BIC=y
2005-11-04 3:27 ` Bug#337089: linux-image-2.6.14-1-powerpc: add CONFIG_TCP_CONG_BIC=y Horms
@ 2005-11-04 18:24 ` Ian McDonald
2005-11-07 6:36 ` Horms
0 siblings, 1 reply; 3+ messages in thread
From: Ian McDonald @ 2005-11-04 18:24 UTC (permalink / raw)
To: Horms; +Cc: Benoît Dejean, 337089, NetDev
> > 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).
>
> could someone please comment on what a good default congestion
> algorithm setup for distribution kernels is?
>
If you want BIC as default then do as suggested here. My personal
opinion is that is the correct thing to do for a standard
distribution.
If it is an experimental distribution then turn on tcp advanced
congestion control and build the rest (except for BIC) as modules.
Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
^ permalink raw reply [flat|nested] 3+ messages in thread
* Bug#337089: linux-image-2.6.14-1-powerpc: add CONFIG_TCP_CONG_BIC=y
2005-11-04 18:24 ` Ian McDonald
@ 2005-11-07 6:36 ` Horms
0 siblings, 0 replies; 3+ messages in thread
From: Horms @ 2005-11-07 6:36 UTC (permalink / raw)
To: Ian McDonald; +Cc: Benoît Dejean, 337089, NetDev
On Sat, Nov 05, 2005 at 07:24:41AM +1300, Ian McDonald wrote:
> > > 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).
> >
> > could someone please comment on what a good default congestion
> > algorithm setup for distribution kernels is?
> >
> If you want BIC as default then do as suggested here. My personal
> opinion is that is the correct thing to do for a standard
> distribution.
Thanks, the suggestion above will be incporated into the next release.
--
Horms
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-11-07 6:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20051102162451.0002CF64E@ibook.free.fr>
2005-11-04 3:27 ` Bug#337089: linux-image-2.6.14-1-powerpc: add CONFIG_TCP_CONG_BIC=y Horms
2005-11-04 18:24 ` Ian McDonald
2005-11-07 6:36 ` Horms
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).