From: Max Matveev <makc@redhat.com>
To: linux-sctp@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: [PATCH 1/2] Update description of net.sctp.sctp_rmem and net.sctp.sctp_wmem tunables
Date: Mon, 20 Jun 2011 18:08:10 +1000 [thread overview]
Message-ID: <20110704083605.AF9C28156C57@regina.usersys.redhat.com> (raw)
sctp does not use second and third ("default" and "max") values
of sctp_(r|w)mem tunables. The format is the same and tcp_(r|w)mem
but the meaning is different so make the documentation explicit to
avoid confusion.
Signed-off-by: Max Matveev <makc@redhat.com>
---
Documentation/networking/ip-sysctl.txt | 11 +++++++++--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
index d3d653a..f37d374 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -1465,10 +1465,17 @@ sctp_mem - vector of 3 INTEGERs: min, pressure, max
Default is calculated at boot time from amount of available memory.
sctp_rmem - vector of 3 INTEGERs: min, default, max
- See tcp_rmem for a description.
+ Only the first value ("min") is used, "default" and "max" are
+ ignored and may be removed in the future versions.
+
+ min: Minimal size of receive buffer used by SCTP socket.
+ It is guaranteed to each STCP socket (but not association) even
+ under moderate memory pressure.
+
+ Default: 1 page
sctp_wmem - vector of 3 INTEGERs: min, default, max
- See tcp_wmem for a description.
+ Currently this tunable has no effect.
addr_scope_policy - INTEGER
Control IPv4 address scoping - draft-stewart-tsvwg-sctp-ipv4-00
--
1.7.3.3
next reply other threads:[~2011-07-04 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 8:08 Max Matveev [this message]
2011-07-04 14:54 ` [PATCH 1/2] Update description of net.sctp.sctp_rmem and net.sctp.sctp_wmem tunables Neil Horman
2011-07-05 2:00 ` Max Matveev
2011-07-05 11:34 ` Neil Horman
2011-07-04 16:11 ` Ben Hutchings
2011-07-05 1:34 ` Shan Wei
2011-07-05 1:58 ` Max Matveev
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=20110704083605.AF9C28156C57@regina.usersys.redhat.com \
--to=makc@redhat.com \
--cc=linux-sctp@vger.kernel.org \
--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