CONFIG_IP_DCCP_CCID3_RTO: Use higher bound for nofeedback timer

General informations

The Linux kernel configuration item CONFIG_IP_DCCP_CCID3_RTO:

• prompt: Use higher bound for nofeedback timer
• type: int
• depends on: CONFIG_IP_DCCP_CCID3 && CONFIG_EXPERIMENTAL
• defined in net/dccp/ccids/Kconfig
• found in Linux kernels: 2.6.20–2.6.36

Help text

Use higher lower bound for nofeedback timer expiration.

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 option enables to set a higher lower bound for the nofeedback value. Values in units of milliseconds can be set here.

A value of 0 disables this feature by enforcing the value specified in RFC 3448. The following values have been suggested as bounds for experimental use: * 16-20ms to match the typical multimedia inter-frame interval * 100ms as a reasonable compromise [default] * 1000ms corresponds to the lower TCP RTO bound (RFC 2988, 2.4)

The default of 100ms is a compromise between a large value for efficient DCCP implementations, and a small value to avoid disrupting the network in times of congestion.

The purpose of the nofeedback timer is to slow DCCP down when there is serious network congestion: experimenting with larger values should therefore not be performed on WANs.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: