From: "Maciej Żenczykowski" <zenczykowski@gmail.com>
To: Ed W <lists@wildgooses.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Performance issue due to constant "modprobes"
Date: Tue, 19 Apr 2011 23:41:20 -0700 [thread overview]
Message-ID: <BANLkTim9Gi-XpwNGZ0RRgtt+PaoRB+Jw0Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=PqPkDpKu8ej1tCkVNugpecbLHyg@mail.gmail.com>
> happen? ie. there should not be any attempted loads of ip_set without
> "iptables -m set" being called (or equivalent).
Actually, are you sure the module is called 'ip_set'?
Kernel iptables match and target extensions are named xt_* or ipt_* or ip6t_*.
If the module is called ip_set and not ipt_set, then maybe we're
seeing some other dependency chain?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=net/netfilter/xt_set.c;h=b3babaed7719b770e02d478091885e7692eac68a;hb=2f666bcf757cb72549f360ef6da02f03620a48b6
contains:
21 MODULE_LICENSE("GPL");
22 MODULE_AUTHOR("Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>");
23 MODULE_DESCRIPTION("Xtables: IP set match and target module");
24 MODULE_ALIAS("xt_SET");
25 MODULE_ALIAS("ipt_set");
26 MODULE_ALIAS("ip6t_set");
27 MODULE_ALIAS("ipt_SET");
28 MODULE_ALIAS("ip6t_SET");
(plus the name derived from the filename which is 'xt_set')
so I'm guessing your 'ip_set' was simply a typo and should have been 'ipt_set'.
- Maciej
next prev parent reply other threads:[~2011-04-20 6:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 23:16 Performance issue due to constant "modprobes" Ed W
2011-04-08 0:18 ` Jan Engelhardt
2011-04-08 17:11 ` Ed W
2011-04-08 0:47 ` Maciej Żenczykowski
2011-04-08 17:11 ` Ed W
2011-04-08 19:54 ` Jan Engelhardt
2011-04-08 23:22 ` Ed W
2011-04-08 23:42 ` Jan Engelhardt
2011-04-09 20:39 ` Ed W
2011-04-09 22:30 ` Jan Engelhardt
2011-04-12 21:03 ` Ed W
2011-04-12 22:05 ` Jan Engelhardt
2011-04-13 11:08 ` Ed W
2011-04-13 12:06 ` Jan Engelhardt
2011-04-13 9:10 ` Maciej Żenczykowski
2011-04-13 11:35 ` Ed W
2011-04-13 12:13 ` Jan Engelhardt
2011-04-13 12:35 ` Ed W
2011-04-13 12:45 ` Jan Engelhardt
2011-04-13 16:45 ` Ed W
2011-04-13 19:20 ` Mr Dash Four
2011-04-14 7:07 ` Maciej Żenczykowski
2011-04-14 7:13 ` Maciej Żenczykowski
2011-04-14 7:19 ` Jan Engelhardt
2011-04-18 13:38 ` Patrick McHardy
2011-04-18 16:33 ` Ed W
2011-04-19 1:12 ` Maciej Żenczykowski
2011-04-19 9:03 ` Maciej Żenczykowski
2011-04-19 16:10 ` Ed W
2011-04-20 1:26 ` Maciej Żenczykowski
2011-04-20 6:41 ` Maciej Żenczykowski [this message]
2011-04-20 7:31 ` Jozsef Kadlecsik
2011-04-20 8:54 ` Ed W
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=BANLkTim9Gi-XpwNGZ0RRgtt+PaoRB+Jw0Q@mail.gmail.com \
--to=zenczykowski@gmail.com \
--cc=lists@wildgooses.com \
--cc=netfilter-devel@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).