modules.
Nearly all users can safely say no here, and a safe default
- selection will be made (BIC-TCP with new Reno as a fallback).
+ selection will be made (CUBIC with new Reno as a fallback).
If unsure, say N.
config TCP_CONG_BIC
tristate "Binary Increase Congestion (BIC) control"
- default y
+ default m
---help---
BIC-TCP is a sender-side only change that ensures a linear RTT
fairness under large windows while offering both scalability and
config TCP_CONG_CUBIC
tristate "CUBIC TCP"
- default m
+ default y
---help---
This is version 2.0 of BIC-TCP which uses a cubic growth function
among other techniques.
choice
prompt "Default TCP congestion control"
- default DEFAULT_BIC
+ default DEFAULT_CUBIC
help
Select the TCP congestion control that will be used by default
for all connections.
endif
-config TCP_CONG_BIC
+config TCP_CONG_CUBIC
tristate
depends on !TCP_CONG_ADVANCED
default y
default "vegas" if DEFAULT_VEGAS
default "westwood" if DEFAULT_WESTWOOD
default "reno" if DEFAULT_RENO
- default "bic"
+ default "cubic"
source "net/ipv4/ipvs/Kconfig"