From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH RFC nft] src: ct: add connection counting support
Date: Mon, 15 Jan 2018 13:42:37 +0100 [thread overview]
Message-ID: <20180115124237.GD27085@breakpoint.cc> (raw)
In-Reply-To: <20180115110833.upp7legzjiirc5ww@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > Basically the rbtree is a kludge because we can't store it in the
> > conntrack table and on-demand counting of the conntrack table would
> > be way too expensive.
>
> I see, actually we could even place this in a hashtable instead,
> right? Not asking you to do this, just thinking aloud here.
Yes. rbtree was only chosen due to deterministic behaviour and
ability to do gc lookups while traversing nodes.
prev parent reply other threads:[~2018-01-15 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 13:41 [PATCH RFC nft] src: ct: add connection counting support Florian Westphal
2018-01-15 10:46 ` Pablo Neira Ayuso
2018-01-15 10:52 ` Pablo Neira Ayuso
2018-01-15 10:59 ` Florian Westphal
2018-01-15 11:08 ` Pablo Neira Ayuso
2018-01-15 12:42 ` Florian Westphal [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=20180115124237.GD27085@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).