| commit | 8a508ac26e72aa203677aa6a8464bd3ea44216a6 | |
| author | Gerrit Renker <gerrit@erg.abdn.ac.uk> | |
| Sun, 3 Dec 2006 16:50:23 +0000 (3 14:50 -0200) | ||
| committer | Arnaldo Carvalho de Melo <acme@mandriva.com> | |
| Sun, 3 Dec 2006 16:50:23 +0000 (3 14:50 -0200) | ||
| tree | 5a2167652960e2dc7300ad6ff3247bc0c31eed5c | treesnapshot (tar.gz zip) |
| parent | 2b5f6dcce5bf94b9b119e9ed8d537098ec61c3d2 | commitdiff |
[DCCP]: Use higher RTO default for CCID3
The TFRC nofeedback timer normally expires after the maximum of 4
RTTs and twice the current send interval (RFC 3448, 4.3). On LANs
with a small RTT this can mean a high processing load and reduced
performance, since then the nofeedback timer is triggered very
frequently.
This patch provides a configuration option to set the bound for the
nofeedback timer, using as default 100 milliseconds.
By setting the configuration option to 0, strict RFC 3448 behaviour
can be enforced for the nofeedback timer.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
The TFRC nofeedback timer normally expires after the maximum of 4
RTTs and twice the current send interval (RFC 3448, 4.3). On LANs
with a small RTT this can mean a high processing load and reduced
performance, since then the nofeedback timer is triggered very
frequently.
This patch provides a configuration option to set the bound for the
nofeedback timer, using as default 100 milliseconds.
By setting the configuration option to 0, strict RFC 3448 behaviour
can be enforced for the nofeedback timer.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
| net/dccp/ccids/Kconfig | diffblobblamehistory | |
| net/dccp/ccids/ccid3.c | diffblobblamehistory |