From: Jan Engelhardt <jengelh@inai.de>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 2/4] netfilter: cleanup use of the term "IPs"
Date: Wed, 11 Jul 2012 01:52:28 +0200 [thread overview]
Message-ID: <1341964350-13809-3-git-send-email-jengelh@inai.de> (raw)
In-Reply-To: <1341964350-13809-1-git-send-email-jengelh@inai.de>
Seen meticulously, we have two IPs these days (Internet Protocol 4,
and 6). Clean up and explicitly use "IP addresses" to disambiguate.
Signed-off-by: Jan Engelhardt <jengelh@inai.de>
---
net/netfilter/ipvs/Kconfig | 15 ++++++++-------
net/netfilter/xt_recent.c | 4 ++--
2 files changed, 10 insertions(+), 9 deletions(-)
diff --git a/net/netfilter/ipvs/Kconfig b/net/netfilter/ipvs/Kconfig
index f987138..e098980 100644
--- a/net/netfilter/ipvs/Kconfig
+++ b/net/netfilter/ipvs/Kconfig
@@ -238,13 +238,14 @@ config IP_VS_SH_TAB_BITS
range 4 20
default 8
---help---
- The source hashing scheduler maps source IPs to destinations
- stored in a hash table. This table is tiled by each destination
- until all slots in the table are filled. When using weights to
- allow destinations to receive more connections, the table is
- tiled an amount proportional to the weights specified. The table
- needs to be large enough to effectively fit all the destinations
- multiplied by their respective weights.
+ The source hashing scheduler maps source IP addresses to
+ destinations stored in a hash table. This table is tiled by
+ each destination until all slots in the table are filled.
+ When using weights to allow destinations to receive more
+ connections, the table is tiled an amount proportional to
+ the weights specified. The table needs to be large enough
+ to effectively fit all the destinations multiplied by their
+ respective weights.
comment 'IPVS application helper'
diff --git a/net/netfilter/xt_recent.c b/net/netfilter/xt_recent.c
index b980b3f..0acc17f 100644
--- a/net/netfilter/xt_recent.c
+++ b/net/netfilter/xt_recent.c
@@ -53,9 +53,9 @@ module_param(ip_pkt_list_tot, uint, 0400);
module_param(ip_list_perms, uint, 0400);
module_param(ip_list_uid, uint, S_IRUGO | S_IWUSR);
module_param(ip_list_gid, uint, S_IRUGO | S_IWUSR);
-MODULE_PARM_DESC(ip_list_tot, "number of IPs to remember per list (>0)");
+MODULE_PARM_DESC(ip_list_tot, "number of IP addresses to remember per list (>0)");
MODULE_PARM_DESC(ip_pkt_list_tot, "number of packets per IP address to remember (1-255)");
-MODULE_PARM_DESC(ip_list_hash_size, "size of hash table used to look up IPs");
+MODULE_PARM_DESC(ip_list_hash_size, "size of hash table used to look up IP addresses");
MODULE_PARM_DESC(ip_list_perms, "permissions on /proc/net/xt_recent/* files");
MODULE_PARM_DESC(ip_list_uid, "default owner of /proc/net/xt_recent/* files");
MODULE_PARM_DESC(ip_list_gid, "default owning group of /proc/net/xt_recent/* files");
--
1.7.7
next prev parent reply other threads:[~2012-07-10 23:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 23:52 xt_recent cleanups, xt_SYSRQ Jan Engelhardt
2012-07-10 23:52 ` [PATCH 1/4] netfilter: xt_recent: remove ip_list_hash_size parameter Jan Engelhardt
2012-07-12 15:42 ` Pablo Neira Ayuso
2012-07-10 23:52 ` Jan Engelhardt [this message]
2012-07-12 15:43 ` [PATCH 2/4] netfilter: cleanup use of the term "IPs" Pablo Neira Ayuso
2012-07-10 23:52 ` [PATCH 3/4] netfilter: use permission mnemonics in module_param Jan Engelhardt
2012-07-10 23:52 ` [PATCH 4/4] netfilter: xtables: inclusion of xt_SYSRQ Jan Engelhardt
2012-07-12 15:49 ` Pablo Neira Ayuso
2012-07-12 16:25 ` Jan Engelhardt
2012-07-12 20:26 ` Florian Westphal
2012-07-12 20:29 ` Jan Engelhardt
2012-07-12 20:35 ` Florian Westphal
2012-07-12 21:25 ` Jan Engelhardt
2012-07-13 9:16 ` Pablo Neira Ayuso
2012-07-14 1:43 ` Maciej Żenczykowski
2012-07-14 13:11 ` Pablo Neira Ayuso
2012-07-14 14:49 ` Aft nix
2012-07-14 15:24 ` Jan Engelhardt
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=1341964350-13809-3-git-send-email-jengelh@inai.de \
--to=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).