| To: | Valdis.Kletnieks@xxxxxx |
|---|---|
| Subject: | Re: tcp_bic (was Re: 2.6.12-rc6-mm1 OOPS in tcp_push_one() |
| From: | Stephen Hemminger <shemminger@xxxxxxxx> |
| Date: | Thu, 9 Jun 2005 09:15:28 -0700 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <200506091523.j59FNmsr008443@turing-police.cc.vt.edu> |
| Organization: | Open Source Development Lab |
| References: | <200506090423.j594NWts004829@turing-police.cc.vt.edu> <20050608.225817.112619139.davem@davemloft.net> <200506091523.j59FNmsr008443@turing-police.cc.vt.edu> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
This was all changed in 2.6.12-rc6-tcp1 which is the next version going into -mm. The default congestion control will be the last one registered (LIFO); so if you built everything as modules. the default will be reno. If you build with the default's from Kconfig, bic will be builtin (not a module) and it will end up the default. If you really want a particular default value then you will need to set it with a sysctl. If you use a sysctl, the module will be autoloaded if needed and you will get the expected protocol. If you ask for an unknown congestion method, then the sysctl attempt will fail. If you remove a tcp congestion control module, then you will get the next available one. Since reno can not be built as a module, and can not be deleted, it will always be available. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | tcp_bic (was Re: 2.6.12-rc6-mm1 OOPS in tcp_push_one(), Valdis . Kletnieks |
|---|---|
| Next by Date: | [PATCH] Re: netdev munching messages again?, Ralf Baechle |
| Previous by Thread: | tcp_bic (was Re: 2.6.12-rc6-mm1 OOPS in tcp_push_one(), Valdis . Kletnieks |
| Next by Thread: | [PATCH] iseries_veth: Supress spurious WARN_ON() at module unload, Michael Ellerman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |