From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH 2/5] netfilter: nft_rbtree: no need for spinlock from set destroy path
Date: Tue, 23 Sep 2014 13:01:59 +0200 [thread overview]
Message-ID: <20140923110159.GA20055@salvia> (raw)
In-Reply-To: <1411465957.26859.179.camel@edumazet-glaptop2.roam.corp.google.com>
On Tue, Sep 23, 2014 at 02:52:37AM -0700, Eric Dumazet wrote:
> On Tue, 2014-09-23 at 11:24 +0200, Pablo Neira Ayuso wrote:
> > The sets are released from the rcu callback, after the rule is removed
> > from the chain list, which implies that nfnetlink cannot update the
> > rbtree and no packets are walking on the set anymore. Thus, we can get
> > rid of the spinlock in the set destroy path there.
> >
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> > Reviewied-by: Thomas Graf <tgraf@suug.ch>
> > ---
> > net/netfilter/nft_rbtree.c | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/net/netfilter/nft_rbtree.c b/net/netfilter/nft_rbtree.c
> > index e1836ff..46214f2 100644
> > --- a/net/netfilter/nft_rbtree.c
> > +++ b/net/netfilter/nft_rbtree.c
> > @@ -234,13 +234,11 @@ static void nft_rbtree_destroy(const struct nft_set *set)
> > struct nft_rbtree_elem *rbe;
> > struct rb_node *node;
> >
> > - spin_lock_bh(&nft_rbtree_lock);
> > while ((node = priv->root.rb_node) != NULL) {
> > rb_erase(node, &priv->root);
> > rbe = rb_entry(node, struct nft_rbtree_elem, node);
> > nft_rbtree_elem_destroy(set, rbe);
> > }
> > - spin_unlock_bh(&nft_rbtree_lock);
> > }
> >
> > static bool nft_rbtree_estimate(const struct nft_set_desc *desc, u32 features,
>
> BTW, do you know if destroying an rbtree is faster this way, or using
> rb_first() ?
>
> Most cases I see in the kernel use a rb_first instead of taking the
> root.
>
> Examples : (its not an exhaustive list)
>
> net/netfilter/xt_connlimit.c:402
> net/sched/sch_netem.c:380
> net/sched/sch_fq.c:519
> drivers/infiniband/hw/mlx4/cm.c:439
> drivers/iommu/iova.c:324
> drivers/md/dm-thin.c:1491
> drivers/mtd/mtdswap.c:625
> drivers/mtd/ubi/attach.c:636
>
> This might be better for large trees, to get better cache locality,
> but I have no experimental data.
I'll send a follow up patch for nf-next to use rb_first() in that
patch. Thanks Eric.
next prev parent reply other threads:[~2014-09-23 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 9:24 [PATCH 0/5] nf pull request for net Pablo Neira Ayuso
2014-09-23 9:24 ` [PATCH 1/5] netfilter: nft_hash: no need for rcu in the hash set destroy path Pablo Neira Ayuso
2014-09-23 9:24 ` [PATCH 2/5] netfilter: nft_rbtree: no need for spinlock from " Pablo Neira Ayuso
2014-09-23 9:52 ` Eric Dumazet
2014-09-23 11:01 ` Pablo Neira Ayuso [this message]
2014-09-23 11:54 ` Eric Dumazet
2014-09-23 16:10 ` Pablo Neira Ayuso
2014-09-23 16:29 ` Eric Dumazet
2014-09-23 9:24 ` [PATCH 3/5] rhashtable: fix lockdep splat in rhashtable_destroy() Pablo Neira Ayuso
2014-09-23 9:24 ` [PATCH 4/5] netfilter: nfnetlink: deliver netlink errors on batch completion Pablo Neira Ayuso
2014-09-23 9:24 ` [PATCH 5/5] netfilter: xt_TPROXY: undefined reference to `udp6_lib_lookup' Pablo Neira Ayuso
2014-09-26 20:21 ` [PATCH 0/5] nf pull request for net David Miller
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=20140923110159.GA20055@salvia \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.