public inbox for netfilter-devel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Eric Garver <eric@garver.life>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH 0/5] Enhance cache filter for list commands
Date: Wed, 11 Mar 2026 20:15:18 +0100	[thread overview]
Message-ID: <abG_RrwTCdXbmGX0@orbyte.nwl.cc> (raw)
In-Reply-To: <abGFDGtr6Lk6dJYq@egarver-mac>

On Wed, Mar 11, 2026 at 11:06:52AM -0400, Eric Garver wrote:
> On Wed, Mar 11, 2026 at 12:11:10AM +0100, Phil Sutter wrote:
> > Reducing the amount of data fetched from kernel improves performance
> > with large rule sets but also reduces adverse side-effects if multiple
> > versions of nftables access the same kernel rule set. Being able to
> > ignore parts of the rule set one is not interested in allows for (more or
> > less) safe coexistence if each tool is operating on the data it created
> > itself only.
> > 
> > This series reduces caching for list commands which specify a family
> > and/or table. To help testing this, patch 1 extends netlink debug output
> > to include chains, flowtables and objects so a test case may check if
> > they are fetched or not.
> > 
> > The remaining patches actually increase filter use.
> > 
> > Phil Sutter (5):
> >   cache: Include chains, flowtables and objects in netlink debug output
> >   cache: Respect family in all list commands
> >   cache: Relax chain_cache_dump filter application
> >   cache: Filter for table when listing sets or maps
> >   cache: Filter for table when listing flowtables
> > 
> >  src/cache.c                                 | 11 ++--
> >  src/mnl.c                                   | 60 ++++++++++++++++++---
> >  tests/shell/testcases/listing/cache_filters | 53 ++++++++++++++++++
> >  3 files changed, 113 insertions(+), 11 deletions(-)
> >  create mode 100755 tests/shell/testcases/listing/cache_filters
> 
> I ran this series against the firewalld testsuite. All green.
> Thanks Phil!

Thanks for testing, Eric! Shame on me for not putting you in Cc as you
asked for. Next time I'll probably best add a Cc: tag to one of the
commits immediately. ;)

Cheers, Phil

  reply	other threads:[~2026-03-11 19:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 23:11 [nft PATCH 0/5] Enhance cache filter for list commands Phil Sutter
2026-03-10 23:11 ` [nft PATCH 1/5] cache: Include chains, flowtables and objects in netlink debug output Phil Sutter
2026-03-10 23:11 ` [nft PATCH 2/5] cache: Respect family in all list commands Phil Sutter
2026-03-11  9:34   ` Pablo Neira Ayuso
2026-03-11 10:19     ` Phil Sutter
2026-03-11 12:11       ` Pablo Neira Ayuso
2026-03-11 14:01         ` Phil Sutter
2026-03-10 23:11 ` [nft PATCH 3/5] cache: Relax chain_cache_dump filter application Phil Sutter
2026-03-11  9:38   ` Pablo Neira Ayuso
2026-03-10 23:11 ` [nft PATCH 4/5] cache: Filter for table when listing sets or maps Phil Sutter
2026-03-11  9:39   ` Pablo Neira Ayuso
2026-03-10 23:11 ` [nft PATCH 5/5] cache: Filter for table when listing flowtables Phil Sutter
2026-03-11  9:40   ` Pablo Neira Ayuso
2026-03-11 15:06 ` [nft PATCH 0/5] Enhance cache filter for list commands Eric Garver
2026-03-11 19:15   ` Phil Sutter [this message]
2026-03-18 16:23 ` Phil Sutter
2026-03-18 16:58   ` Pablo Neira Ayuso
2026-03-18 16:59     ` Pablo Neira Ayuso
2026-03-18 18:49       ` Phil Sutter

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=abG_RrwTCdXbmGX0@orbyte.nwl.cc \
    --to=phil@nwl.cc \
    --cc=eric@garver.life \
    --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