All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Garver <eric@garver.life>,
	netfilter-devel@vger.kernel.org, nhofmeyr@sysmocom.de,
	phil@nwl.cc, fw@strlen.de
Subject: Re: [PATCH nft 0/5] relax cache requirements, speed up incremental updates
Date: Mon, 19 Aug 2024 17:54:48 +0200	[thread overview]
Message-ID: <ZsNqyMw4t6Py1WBs@calendula> (raw)
In-Reply-To: <Zr4aCjGwkedu9ssB@egarver-mac>

On Thu, Aug 15, 2024 at 11:08:58AM -0400, Eric Garver wrote:
> On Thu, Aug 15, 2024 at 01:37:07PM +0200, Pablo Neira Ayuso wrote:
> > Hi,
> > 
> > The following patchset relaxes cache requirements, this is based on the
> > observation that objects are fetched to report errors and provide hints.
> > 
> > This is a new attempt to speed up incremental updates following a
> > different approach, after reverting:
> > 
> >   e791dbe109b6 ("cache: recycle existing cache with incremental updates")
> > 
> > which is fragile because cache consistency checking needs more, it should
> > be still possible to explore in the future, but this seems a more simple
> > approach at this stage.
> > 
> > This is passing tests/shell and tests/py.
> > 
> > Pablo Neira Ayuso (5):
> >   cache: rule by index requires full cache
> >   cache: populate chains on demand from error path
> >   cache: populate objecs on demand from error path
> >   cache: populate flowtable on demand from error path
> >   cache: do not fetch set inconditionally on delete
> > 
> >  include/cache.h |  1 -
> >  src/cache.c     | 23 ++++++-----------------
> >  src/cmd.c       | 23 +++++++++++++++++++++++
> >  3 files changed, 29 insertions(+), 18 deletions(-)
> 
> I applied this series to nft master and tested it against the latest
> net-next and RHEL-9 kernels. No issues or regressions found.

Pushed out, thanks for testing.

      reply	other threads:[~2024-08-19 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 11:37 [PATCH nft 0/5] relax cache requirements, speed up incremental updates Pablo Neira Ayuso
2024-08-15 11:37 ` [PATCH nft 1/5] cache: rule by index requires full cache Pablo Neira Ayuso
2024-08-15 11:37 ` [PATCH nft 2/5] cache: populate chains on demand from error path Pablo Neira Ayuso
2024-08-15 11:37 ` [PATCH nft 3/5] cache: populate objecs " Pablo Neira Ayuso
2024-08-15 11:37 ` [PATCH nft 4/5] cache: populate flowtable " Pablo Neira Ayuso
2024-08-15 11:37 ` [PATCH nft 5/5] cache: do not fetch set inconditionally on delete Pablo Neira Ayuso
2024-08-15 12:25 ` [PATCH nft 0/5] relax cache requirements, speed up incremental updates Phil Sutter
2024-08-15 12:46   ` Pablo Neira Ayuso
2024-08-15 13:10     ` Phil Sutter
2024-08-15 13:38       ` Pablo Neira Ayuso
2024-08-15 15:08 ` Eric Garver
2024-08-19 15:54   ` 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=ZsNqyMw4t6Py1WBs@calendula \
    --to=pablo@netfilter.org \
    --cc=eric@garver.life \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=nhofmeyr@sysmocom.de \
    --cc=phil@nwl.cc \
    /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.