From: Florian Westphal <fw@strlen.de>
To: Liping Zhang <zlpnobody@163.com>
Cc: pablo@netfilter.org, netfilter-devel@vger.kernel.org,
Liping Zhang <liping.zhang@spreadtrum.com>
Subject: Re: [PATCH nf-next 2/2] netfilter: conntrack: simplify the code by using nf_conntrack_get_ht
Date: Tue, 12 Jul 2016 15:03:03 +0200 [thread overview]
Message-ID: <20160712130303.GE17163@breakpoint.cc> (raw)
In-Reply-To: <1468323901-15767-2-git-send-email-zlpnobody@163.com>
Liping Zhang <zlpnobody@163.com> wrote:
> From: Liping Zhang <liping.zhang@spreadtrum.com>
>
> Since Commit 64b87639c9cb ("netfilter: conntrack: fix race between
> nf_conntrack proc read and hash resize") introdue the
> nf_conntrack_get_ht, so there's no need to check nf_conntrack_generation
> again and again to get the hash table and hash size.
>
> Signed-off-by: Liping Zhang <liping.zhang@spreadtrum.com>
> ---
> net/netfilter/nf_conntrack_core.c | 30 +++++++++++-------------------
> 1 file changed, 11 insertions(+), 19 deletions(-)
>
> diff --git a/net/netfilter/nf_conntrack_core.c b/net/netfilter/nf_conntrack_core.c
> index 2d46225..bafebf7 100644
> --- a/net/netfilter/nf_conntrack_core.c
> +++ b/net/netfilter/nf_conntrack_core.c
> @@ -461,7 +461,8 @@ nf_ct_key_equal(struct nf_conntrack_tuple_hash *h,
> }
>
> /* must be called with rcu read lock held */
> -void nf_conntrack_get_ht(struct hlist_nulls_head **hash, unsigned int *hsize)
> +inline void
> +nf_conntrack_get_ht(struct hlist_nulls_head **hash, unsigned int *hsize)
Which "inline void"? This is very unusual.
I would suggest to not add it, and ...
> {
> struct hlist_nulls_head *hptr;
> unsigned int sequence, hsz;
> @@ -489,14 +490,11 @@ ____nf_conntrack_find(struct net *net, const struct nf_conntrack_zone *zone,
> struct nf_conntrack_tuple_hash *h;
> struct hlist_nulls_head *ct_hash;
> struct hlist_nulls_node *n;
> - unsigned int bucket, sequence;
> + unsigned int bucket, hsize;
>
> begin:
> - do {
> - sequence = read_seqcount_begin(&nf_conntrack_generation);
> - bucket = scale_hash(hash);
> - ct_hash = nf_conntrack_hash;
> - } while (read_seqcount_retry(&nf_conntrack_generation, sequence));
> + nf_conntrack_get_ht(&ct_hash, &hsize);
> + bucket = reciprocal_scale(hash, hsize);
leave ____nf_conntrack_find alone, but convert
> @@ -801,18 +799,15 @@ nf_conntrack_tuple_taken(const struct nf_conntrack_tuple *tuple,
This one ..
> @@ -878,14 +873,11 @@ static noinline int early_drop(struct net *net, unsigned int _hash)
... and this one too.
next prev parent reply other threads:[~2016-07-12 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 11:45 [PATCH nf-next 1/2] netfilter: conntrack: protect early_drop by rcu read lock Liping Zhang
2016-07-12 11:45 ` [PATCH nf-next 2/2] netfilter: conntrack: simplify the code by using nf_conntrack_get_ht Liping Zhang
2016-07-12 13:03 ` Florian Westphal [this message]
2016-07-13 8:13 ` Liping Zhang
2016-07-12 13:01 ` [PATCH nf-next 1/2] netfilter: conntrack: protect early_drop by rcu read lock Florian Westphal
2016-07-12 14:34 ` Pablo Neira Ayuso
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=20160712130303.GE17163@breakpoint.cc \
--to=fw@strlen.de \
--cc=liping.zhang@spreadtrum.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=zlpnobody@163.com \
/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).