netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
	den@openvz.org, xemul@openvz.org, ebiederm@xmission.com,
	benjamin.thery@bull.net, dlezcano@fr.ibm.com
Subject: Re: [PATCH 07/25] netns ct: per-netns expectations
Date: Mon, 23 Jun 2008 12:27:53 +0200	[thread overview]
Message-ID: <485F7AA9.7000308@trash.net> (raw)
In-Reply-To: <20080622010643.GH5392@martell.zuzino.mipt.ru>

Alexey Dobriyan wrote:
> Make per-netns expectation count, expectation hash.
> 
> netns of expectations is netns of its master conntrack.
> This way expectation is not bloated with netns pointer and something
> is seriously wrong anyway if those two differ.
> 
> +static inline struct net *exp_net(struct nf_conntrack_expect *exp)
> +{
> +#ifdef CONFIG_NET_NS
> +	return exp->master->ct_net;	/* by definition */
> +#else
> +	return &init_net;
> +#endif
> +}

nf_ct_exp_net() or nf_ct_expect_net() please.

> --- a/net/netfilter/nf_conntrack_expect.c
> +++ b/net/netfilter/nf_conntrack_expect.c
> @@ -28,17 +28,12 @@
>  #include <net/netfilter/nf_conntrack_helper.h>
>  #include <net/netfilter/nf_conntrack_tuple.h>
>  
> -struct hlist_head *nf_ct_expect_hash __read_mostly;
> -EXPORT_SYMBOL_GPL(nf_ct_expect_hash);
> -
>  unsigned int nf_ct_expect_hsize __read_mostly;
>  EXPORT_SYMBOL_GPL(nf_ct_expect_hsize);

This one also needs to be in the namespace I think. BTW, are
module parameters also per namespace?


      reply	other threads:[~2008-06-23 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-22  1:06 [PATCH 07/25] netns ct: per-netns expectations Alexey Dobriyan
2008-06-23 10:27 ` Patrick McHardy [this message]

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=485F7AA9.7000308@trash.net \
    --to=kaber@trash.net \
    --cc=adobriyan@gmail.com \
    --cc=benjamin.thery@bull.net \
    --cc=den@openvz.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=xemul@openvz.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).