From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH libnftnl] src: add dynamic register allocation infrastructure
Date: Sun, 15 May 2022 00:29:44 +0200 [thread overview]
Message-ID: <YoAtWOcCusBi4tR7@salvia> (raw)
In-Reply-To: <Yn/dnyORrGtf7t8E@orbyte.nwl.cc>
On Sat, May 14, 2022 at 06:49:35PM +0200, Phil Sutter wrote:
> Hi Pablo,
>
> On Mon, May 02, 2022 at 01:07:44PM +0200, Pablo Neira Ayuso wrote:
> > Starting Linux kernel 5.18-rc, operations on registers that already
> > contain the expected data are turned into noop.
> >
> > Track operation on registers to use the same register through
> > nftnl_reg_get(). This patch introduces an LRU eviction strategy when all
> > the registers are in used.
> >
> > nftnl_reg_get_scratch() is used to allocate a register as scratchpad
> > area: no tracking is performed in this case, although register eviction
> > might occur.
> >
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> > ---
> > include/expr_ops.h | 6 +
> > include/internal.h | 1 +
> > include/libnftnl/Makefile.am | 1 +
> > include/regs.h | 32 ++++++
> > src/Makefile.am | 1 +
> > src/expr/meta.c | 44 +++++++
> > src/expr/payload.c | 31 +++++
> > src/libnftnl.map | 7 ++
> > src/regs.c | 216 +++++++++++++++++++++++++++++++++++
> > 9 files changed, 339 insertions(+)
> > create mode 100644 include/regs.h
> > create mode 100644 src/regs.c
>
> Did you forget to add include/libnftnl/regs.h to this patch? It is
> referenced from src/regs.c and build fails.
Yes, this is fixed here:
http://git.netfilter.org/libnftnl/commit/?id=e549f5b3239c19f78af2f7c7a582fe5616403ca8
next prev parent reply other threads:[~2022-05-14 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 11:07 [PATCH libnftnl] src: add dynamic register allocation infrastructure Pablo Neira Ayuso
2022-05-14 16:49 ` Phil Sutter
2022-05-14 22:29 ` Pablo Neira Ayuso [this message]
2022-05-15 12:16 ` 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=YoAtWOcCusBi4tR7@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--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 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).