diff options
| author | Matthew Dillon <dillon@FreeBSD.org> | 2002-08-25 01:51:57 +0000 |
|---|---|---|
| committer | Matthew Dillon <dillon@FreeBSD.org> | 2002-08-25 01:51:57 +0000 |
| commit | 667137d174c4393aed8437529b0606d00fed2060 (patch) | |
| tree | cfdb5e8a638d76ecbd70af1f8004ebd7b5e4f451 | |
| parent | 760e2cb04a994165551e900893884f2086dcc118 (diff) | |
Notes
| -rw-r--r-- | share/man/man4/tcp.4 | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/share/man/man4/tcp.4 b/share/man/man4/tcp.4 index c8a942fbc202..24e2e8116fb9 100644 --- a/share/man/man4/tcp.4 +++ b/share/man/man4/tcp.4 @@ -300,6 +300,19 @@ no reseeding will occur. Reseeding should not be necessary, and will break .Dv TIME_WAIT recycling for a few minutes. +.It tcp.inet.tcp.rexmit_{min,slop} +Adjust the retransmit timer calculation for TCP. The slop is +typically added to the raw calculation to take into account +occassional variances that the SRTT (smoothed round trip time) +is unable to accomodate, while the minimum specifies an +absolute minimum. While a number of TCP RFCs suggest a 1 +second minimum these RFCs tend to focus on streaming behavior +and fail to deal with the fact that a 1 second minimum has severe +detrimental effects over lossy interactive connections, such +as a 802.11b wireless link, and over very fast but lossy +connections for those cases not covered by the fast retransmit +code. For this reason we use 200ms of slop and a near-0 +minimum, which gives us an effective minimum of 200ms (similar to Linux). .It tcp.inflight_enable Enable .Tn TCP |
