From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC] Inter-match communication cache
Date: Mon, 24 Sep 2012 11:57:07 +0200 [thread overview]
Message-ID: <20120924095707.GA19084@1984> (raw)
In-Reply-To: <alpine.DEB.2.00.1209182232460.5113@blackhole.kfki.hu>
Hi Jozsef,
On Tue, Sep 18, 2012 at 11:01:34PM +0200, Jozsef Kadlecsik wrote:
> Hi,
>
> I propose a small cache for inter-match communication purpose:
>
> diff --git a/include/linux/netfilter/x_tables.h b/include/linux/netfilter/x_tables.h
> index 8d674a7..f07eab2 100644
> --- a/include/linux/netfilter/x_tables.h
> +++ b/include/linux/netfilter/x_tables.h
> @@ -216,6 +216,9 @@ struct xt_action_param {
> const void *matchinfo, *targinfo;
> };
> const struct net_device *in, *out;
> +#ifdef CONFIG_NETFILTER_XTABLES_CACHE
> + u_int32_t cache;
> +#endif
I think you can implement this by means of one per-CPU cache inside
the xt_set match.
Check the old per-CPU event cache in net/netfilter/nf_conntrack_ecache.c.
We used to have something similar.
I'd prefer this approach rather than one change in xtables for this.
It still seems to me too specific of your xt_set extensions.
It will remain internal of xt_set match, but we can revisit this later
on to generalize it if it becomes interesting for more matches.
next prev parent reply other threads:[~2012-09-24 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 21:01 [RFC] Inter-match communication cache Jozsef Kadlecsik
2012-09-19 15:38 ` Jesper Dangaard Brouer
2012-09-19 16:11 ` Jan Engelhardt
2012-09-19 17:25 ` Jozsef Kadlecsik
2012-09-24 9:57 ` Pablo Neira Ayuso [this message]
2012-09-24 10:25 ` Jozsef Kadlecsik
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=20120924095707.GA19084@1984 \
--to=pablo@netfilter.org \
--cc=kadlec@blackhole.kfki.hu \
--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).