From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] tcp_vegas_cong_avoid doc
Date: Mon, 26 Apr 2004 16:32:21 -0700 [thread overview]
Message-ID: <20040426163221.56a08130.davem@redhat.com> (raw)
In-Reply-To: <20040426101210.461726d2@dell_ss3.pdx.osdl.net>
On Mon, 26 Apr 2004 10:12:10 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> Patch to update sysctl documentation to include tcp_vegas.
> Feel free to rewrite for better explanation.
I applied this, only changing a minor grammatical error at the
end. See attached...
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/04/26 16:31:03-07:00 shemminger@osdl.org
# [TCP]: Add vegas sysctl docs.
#
# Documentation/networking/ip-sysctl.txt
# 2004/04/26 16:30:36-07:00 shemminger@osdl.org +9 -0
# [TCP]: Add vegas sysctl docs.
#
diff -Nru a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
--- a/Documentation/networking/ip-sysctl.txt Mon Apr 26 16:31:29 2004
+++ b/Documentation/networking/ip-sysctl.txt Mon Apr 26 16:31:29 2004
@@ -307,6 +307,15 @@
wired networks and throughput over wireless links.
Default: 0
+tcp_vegas_cong_avoid - BOOLEAN
+ Enable TCP Vegas congestion avoidance algorithm.
+ TCP Vegas is a sender-side only change to TCP that anticipates
+ the onset of congestion by estimating the bandwidth. TCP Vegas
+ adjusts the sending rate by modifying the congestion
+ window. TCP Vegas should provide less packet loss, but it is
+ not as aggressive as TCP Reno.
+ Default:0
+
ip_local_port_range - 2 INTEGERS
Defines the local port range that is used by TCP and UDP to
choose the local port. The first number is the first, the
prev parent reply other threads:[~2004-04-26 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 17:12 [PATCH] tcp_vegas_cong_avoid doc Stephen Hemminger
2004-04-26 23:32 ` David S. Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040426163221.56a08130.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).