From: Ani Sinha <ani@arista.com>
To: corbet@lwn.net, davem@davemloft.net, edumazet@google.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
ani@arista.com, P@draigbrady.com, netdev@vger.kernel.org,
fruggeri@arista.com
Subject: [PATCH 1/1] update ip-sysctl.txt documentation
Date: Tue, 6 Jan 2015 15:36:22 -0800 [thread overview]
Message-ID: <1420587382-24612-1-git-send-email-ani@arista.com> (raw)
Update documentation to reflect the fact that
/proc/sys/net/ipv4/route/max_size is no longer used for ipv4.
Signed-off-by: Ani Sinha <ani@arista.com>
---
Documentation/networking/ip-sysctl.txt | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
index 9bffdfc..2a28261 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -64,8 +64,10 @@ fwmark_reflect - BOOLEAN
Default: 0
route/max_size - INTEGER
- Maximum number of routes allowed in the kernel. Increase
- this when using large numbers of interfaces and/or routes.
+ Post linux kernel 3.6, this is deprecated for ipv4 as route cache is no
+ longer used. For ipv6, this is used to limit the maximum number of ipv6
+ routes allowed in the kernel. Increase this when using large numbers of
+ interfaces and/or routes.
neigh/default/gc_thresh1 - INTEGER
Minimum number of entries to keep. Garbage collector will not
--
1.7.4.4
next reply other threads:[~2015-01-06 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 23:36 Ani Sinha [this message]
2015-01-07 10:11 ` [PATCH 1/1] update ip-sysctl.txt documentation David Laight
2015-01-07 23:46 ` Ani Sinha
[not found] <1420574648-24213-1-git-send-email-ani@arista.com>
2015-01-06 22:02 ` Fwd: " Ani Sinha
2015-01-06 22:31 ` David Miller
2015-01-06 22:34 ` Ani Sinha
2015-01-06 23:48 ` Stephen Hemminger
2015-01-06 23:50 ` Ani Sinha
-- strict thread matches above, loose matches on Subject: below --
2015-01-06 22:33 Ani Sinha
2015-01-06 22:40 ` David Miller
2015-01-07 2:08 ` Ani Sinha
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=1420587382-24612-1-git-send-email-ani@arista.com \
--to=ani@arista.com \
--cc=P@draigbrady.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fruggeri@arista.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).