From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, carges@cloudflare.com
Subject: Re: [PATCH nf,v2] netfilter: nft_set_rbtree: revisit array resize logic
Date: Mon, 16 Mar 2026 13:35:24 +0100 [thread overview]
Message-ID: <abf5DO7J4xXEb1qZ@strlen.de> (raw)
In-Reply-To: <20260316114835.3834812-1-pablo@netfilter.org>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> Chris Arges reports high memory consumption with thousands of
> containers, this patch revisits the array allocation logic.
>
> Start by 1024 slots in the array (which takes 16 Kbytes initially on
> x86_64), and expand it by x1.5.
Do you think it makese sense to start with set->size for anonymous sets?
I suspect most anon sets are pretty small, 16kb / rule is a lot.
No need to send a v3, this could be done in a followup patch.
prev parent reply other threads:[~2026-03-16 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 11:48 [PATCH nf,v2] netfilter: nft_set_rbtree: revisit array resize logic Pablo Neira Ayuso
2026-03-16 12:35 ` 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=abf5DO7J4xXEb1qZ@strlen.de \
--to=fw@strlen.de \
--cc=carges@cloudflare.com \
--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 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.