From: John Heffner <jheffner@psc.edu>
To: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: [PATCH 2/3] TCP sysctl documentation: tcp_no_metrics_save
Date: Mon, 26 Feb 2007 20:09:34 -0500 [thread overview]
Message-ID: <45E384CE.7030209@psc.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2: doc2.patch --]
[-- Type: text/plain, Size: 1373 bytes --]
Document sysctl tcp_no_metrics_save.
Signed-off-by: John Heffner <jheffner@psc.edu>
---
commit 17cb799000caef3b2fed28cc5d0601bb2311efa8
tree c27ccf561065b145bc48d0b8dbbaa3c608015e03
parent 4c5fd9d3a9ea8b939aed1afda2ac0fc54e3df592
author John Heffner <jheffner@psc.edu> Mon, 26 Feb 2007 19:51:50 -0500
committer John Heffner <jheffner@psc.edu> Mon, 26 Feb 2007 19:51:50 -0500
Documentation/networking/ip-sysctl.txt | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
index a9ad96b..891f389 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -249,6 +249,14 @@ tcp_moderate_rcvbuf - BOOLEAN
match the size required by the path for full throughput. Enabled by
default.
+tcp_no_metrics_save - BOOLEAN
+ By default, TCP saves various connection metrics in the route cache
+ when the connection closes, so that connections established in the
+ near future can use these to set initial conditions. Usually, this
+ increases overall performance, but may sometimes cause performance
+ degredation. If set, TCP will not cache metrics on closing
+ connections.
+
tcp_orphan_retries - INTEGER
How may times to retry before killing TCP connection, closed
by our side. Default value 7 corresponds to ~50sec-16min
reply other threads:[~2007-02-27 1:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45E384CE.7030209@psc.edu \
--to=jheffner@psc.edu \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).