From: Niklas Cassel <niklas.cassel@axis.com>
To: <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <kuznet@ms2.inr.ac.ru>,
<jmorris@namei.org>, <yoshfuji@linux-ipv6.org>, <kaber@trash.net>,
Niklas Cassel <niklass@axis.com>,
Niklas Cassel <niklass@axis.com>
Subject: [PATCH RESEND] net: Documentation: Fix default value tcp_limit_output_bytes
Date: Mon, 9 Nov 2015 15:59:00 +0100 [thread overview]
Message-ID: <1447081140-16955-1-git-send-email-niklass@axis.com> (raw)
Commit c39c4c6abb89 ("tcp: double default TSQ output bytes limit")
updated default value for tcp_limit_output_bytes
Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
---
Already sent the patch to linux-doc@vger.kernel.org,
but sending it to netdev@vger.kernel.org too.
Documentation/networking/ip-sysctl.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
index 05915be..2ea4c45 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -709,7 +709,7 @@ tcp_limit_output_bytes - INTEGER
typical pfifo_fast qdiscs.
tcp_limit_output_bytes limits the number of bytes on qdisc
or device to reduce artificial RTT/cwnd and reduce bufferbloat.
- Default: 131072
+ Default: 262144
tcp_challenge_ack_limit - INTEGER
Limits number of Challenge ACK sent per second, as recommended
--
2.1.4
next reply other threads:[~2015-11-09 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 14:59 Niklas Cassel [this message]
2015-11-09 17:17 ` [PATCH RESEND] net: Documentation: Fix default value tcp_limit_output_bytes David Miller
-- strict thread matches above, loose matches on Subject: below --
2015-11-09 13:58 Niklas Cassel
2015-11-11 16:50 ` Jonathan Corbet
2015-11-11 16:57 ` David Miller
2015-11-11 17:02 ` Jonathan Corbet
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=1447081140-16955-1-git-send-email-niklass@axis.com \
--to=niklas.cassel@axis.com \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=niklass@axis.com \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.