From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next 0/5] nf_tables set updates
Date: Wed, 25 Oct 2023 11:48:33 +0200 [thread overview]
Message-ID: <ZTjkcdBmeNrnsd50@calendula> (raw)
In-Reply-To: <20231024083359.24742-1-pablo@netfilter.org>
On Tue, Oct 24, 2023 at 10:33:54AM +0200, Pablo Neira Ayuso wrote:
> Hi,
>
> This is a first batch of nf_tables set updates:
>
> 1) Use nft_set_ext already accesible as parameter via .flush(), no
> need for pipapo_deactivate() call.
>
> 2) Turn .flush into void, this never fails.
>
> 3) Add and use struct nft_elem_priv placeholder, suggested by Florian.
>
> 4) Shrink memory usage for set elements in transactions, as well as
> stack usage.
>
> 5) Use struct nft_elem_priv in .insert, in preparation for set timeout
> updates, this will come in a later patch.
>
> This batch has survived hours of 30s-stress runs and tests/shell,
> I am still stress testing the set element updates, that will come in
> a follow up batch.
Series applied to nf-next
prev parent reply other threads:[~2023-10-25 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 8:33 [PATCH nf-next 0/5] nf_tables set updates Pablo Neira Ayuso
2023-10-24 8:33 ` [PATCH nf-next 1/5] netfilter: nft_set_pipapo: no need to call pipapo_deactivate() from flush Pablo Neira Ayuso
2023-10-24 8:33 ` [PATCH nf-next 2/5] netfilter: nf_tables: set backend .flush always succeeds Pablo Neira Ayuso
2023-10-24 8:33 ` [PATCH nf-next 3/5] netfilter: nf_tables: expose opaque set element as struct nft_elem_priv Pablo Neira Ayuso
2023-10-24 8:33 ` [PATCH nf-next 4/5] netfilter: nf_tables: shrink memory consumption of set elements Pablo Neira Ayuso
2023-10-24 8:33 ` [PATCH nf-next 5/5] netfilter: nf_tables: set->ops->insert returns opaque set element in case of EEXIST Pablo Neira Ayuso
2023-10-25 9:48 ` Pablo Neira Ayuso [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=ZTjkcdBmeNrnsd50@calendula \
--to=pablo@netfilter.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 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).